FXMacroData vs Myfxbook Economic Calendar: API Alternative for FX Traders

This comparison is for FX traders, EA and bot builders, and quant developers who already use the Myfxbook economic calendar and are wondering whether it can feed a script, an expert advisor, a dashboard, or an AI assistant. The practical question is not which calendar looks better on a second monitor. It is whether there is a supported, documented way to pull calendar rows into code, under terms that fit what you are building.

The short finding: Myfxbook is a strong free calendar for people reading events, with impact labels, previous/consensus/actual values, email reminders, a configurable widget, an RSS feed, and CSV/XML export, plus a large community and sentiment data. Its public API, however, documents account, trade, and community-outlook methods and no economic calendar method. FXMacroData is built for the programmatic side of the same job: a documented REST API for release data, a release calendar endpoint, second-level announcement timestamps, and published plans that cover commercial and automated use.

Decision snapshot

Choose Myfxbook when

You read the calendar by hand, want it free, value community sentiment and account tracking in the same place, or want a free calendar widget on a personal site.

Choose FXMacroData when

Code needs the data: a documented calendar and announcements API, second-level release timestamps, official-source history, and terms that allow automated and commercial use.

Quick answer

Myfxbook's public API has no economic calendar method on its documentation page. If you need calendar data in code, FXMacroData is the supported route; keep Myfxbook for reading, sentiment, and account tracking.

Takeaway: These products overlap on the calendar screen but split on access: Myfxbook is a free reading surface, FXMacroData is a data feed.

Pricing And Access

Myfxbook's economic calendar is free to use on the web, and the calendar widget and RSS feed are offered at no charge. There is no paid calendar plan or calendar data licence listed on the pages we checked, so there is no like-for-like price to chart. The one paid element on the API page is a higher request limit for the community outlook (sentiment) methods: the free version is limited to 100 requests per 24 hours and the paid version to 2,800 requests per 24 hours, with no price published on that page.

FXMacroData publishes self-serve pricing. The Always Free tier needs no key, covers USD data at 100 requests/day, and delays USD announcements by 15 minutes. Individual is $50/month or $500/year with a 14-day trial and 1,000,000 requests/month (bursts of 300/minute, 5,000/hour, 20 concurrent). Business is $250/month or $2,500/year for companies and teams of up to 10 people with the same allowance and priority support. Enterprise is by custom agreement, and a self-serve Commercial Redistribution add-on costs $10/month per block of up to 100 measured users or 1,000 public-feed followers.

What each route costs

FXMacroData Individual

$50/month

Calendar and announcements API, 22 currencies, 1,000,000 requests/month, 14-day trial. Always Free USD tier with no key.

Myfxbook calendar

Free*

Web calendar, widget, RSS feed, and CSV/XML export panel. No calendar API method or calendar data licence listed.

Myfxbook API outlook tier

Not publicly listed*

Paid tier raises community outlook calls from 100 to 2,800 per 24 hours. It covers sentiment, not the calendar.

Takeaway: Myfxbook costs nothing because it does not sell calendar data; FXMacroData charges because programmatic, licensed calendar and release data is the product.

Does Myfxbook Have An Economic Calendar API?

Myfxbook does have a public API, and it is useful. Requests take the form https://www.myfxbook.com/api/[method].[json|xml], a session is created by logging in with a Myfxbook email and password, and sessions are IP-bound and expire after one month. Responses come in JSON or XML.

What that API covers is the Myfxbook account and community product. The documentation page lists 13 methods. None of them returns economic calendar events, consensus figures, or actual releases. The calendar is mentioned as a website tool, not as an endpoint.

Myfxbook API: the 13 documented methods, grouped

Session (2)

login, logout

Accounts and trades (8)

get-my-accounts, get-watched-accounts, get-open-trades, get-open-orders, get-history (last 50 closed trades), get-daily-gain, get-gain, get-data-daily

Widget and sentiment (3)

get-custom-widget, get-community-outlook, get-community-outlook-by-country

Economic calendar (0)

No method for scheduled events, consensus, actuals, or release history is documented.

Takeaway: The Myfxbook API is an account-tracking and sentiment API. Anyone searching for a "Myfxbook calendar API" will not find one on the official documentation page.

The API page also sets an important condition: software developed with it should be free, because Myfxbook keeps its own service free of charge. That is a reasonable stance for a community platform, but it rules the API out as the backbone of a paid product even for the data it does cover.

Side-By-Side Comparison

* Competitor pricing and limits retrieved from Myfxbook's public API, widgets, and RSS pages in October 2026.

Four Ways To Get Myfxbook Calendar Data, And Their Limits

Without an API, there are four sanctioned routes to Myfxbook calendar information. Each is fine for a person; each has a catch when a program is the consumer.

Myfxbook calendar access routes

1. Web calendar

Date, time left, event, impact, previous, consensus, actual. Filters by currency, impact, and country; time zone selector; email reminders.

Catch: built for eyes, not parsers.

2. Calendar widget

Free embed configured by language, impact, currency, and country. Embed code is generated after ticking "I agree to the Terms And Conditions" and carries a Myfxbook credit link.

Catch: displays data on your page; does not hand it to your code.

3. RSS feed

Calendar events as RSS 2.0, offered free for individual, non-commercial use. Each item's values sit inside an escaped HTML table; publish times are minute-level GMT.

Catch: licence and format both work against automation.

4. CSV / XML export

The calendar's settings panel includes an export option in CSV or XML for the selected event list.

Catch: a manual snapshot, not a live feed.

Takeaway: Every Myfxbook calendar route assumes a human in the loop. Scraping the page to fill the gap means building on an undocumented surface with no service commitment.

Release Timing And Timestamps

Myfxbook describes its calendar as showing scheduled events and their results in real time, with a countdown to each one, and the widget page says results arrive as they are released to the market. Those are reasonable claims for a reading surface. What is not published is a measured delay between the official release and the value appearing, and the calendar and RSS feed show event times to the minute rather than the second.

For an EA that trades around Non-Farm Payrolls or a backtest that measures the first five minutes after US CPI, those details decide whether the data is usable. FXMacroData stores a second-level announcement_datetime on every release row. Releases are typically available within seconds of official publication, against a target of one second from publication, and the measured record, by source and including every release that took longer, is public on the release speed page.

Same NFP release, two consumption paths

T-1 day: plan

Both: the event appears with time, impact, prior, and consensus. Myfxbook's countdown and email reminder are handy here.

T+0: publication

The agency posts the number. FXMacroData records it with a second-level timestamp; Myfxbook updates the actual on its page.

T+seconds: code reacts

An EA polling or streaming FXMacroData receives a JSON row. A Myfxbook-only setup has no supported endpoint to poll.

Later: research

FXMacroData history replays the event with exact timestamps against EUR/USD or USD/JPY. Myfxbook offers a manual CSV/XML export.

Coverage And History

Myfxbook's breadth is a real strength. The widget configuration lists well over 100 currencies and a long list of countries and regions, and the calendar includes holidays, central-bank speeches, auctions, and a separate interest-rates view. Event detail pages add an explanation, the data source, and historical values where available. For a trader scanning the week, that breadth is welcome.

FXMacroData covers fewer economies by design: 22 currencies in the production API (USD, EUR, GBP, JPY, AUD, CAD, CHF, NZD, BRL, CNH, CNY, DKK, HUF, ILS, KRW, MYR, NGN, NOK, PEN, SEK, THB, TWD) and 700+ indicator series, including policy rates, CPI and core CPI, GDP, labour data, PMIs, retail sales, trade, current account, and wages. Each series is sourced from the official statistics agency or central bank, with source metadata, and full history is available through the API. Around that, FXMacroData adds datasets a calendar does not: CFTC COT positioning, government bond yields and curves, commodities, central-bank press releases from the Federal Reserve, ECB, Bank of Japan, and Bank of England, and FX session timing.

Licensing For Programmatic And Commercial Use

This is where many Myfxbook-to-code projects stall. The pages checked set out three conditions: software built on the Myfxbook API should be free; the RSS feeds are free for individual, non-commercial use; and the widget's embed code is issued only after accepting Myfxbook's terms, with a credit link back to the calendar. The general terms of use also state that reproduction of site content is prohibited. None of that is unusual for a free community site, but it means a signal service, a paid bot, a broker dashboard, or a client report cannot lean on Myfxbook calendar data without a separate arrangement, and no such arrangement is advertised.

FXMacroData's paid plans cover automated use by the subscriber, and Business adds company checkout for teams of up to 10 people. If you display FXMacroData values to other people, for example in a Telegram channel, an app, or a client portal, the self-serve Commercial Redistribution add-on covers that at $10/month per block of up to 100 measured users or 1,000 public-feed followers.

API Example: Pulling NFP Into Code

A paid FXMacroData request sends the key in the X-API-Key header. The same pattern serves the calendar (/v1/calendar/usd), spot rates (/v1/forex/eur/usd), and positioning (/v1/cot/eur):

curl -H "X-API-Key: YOUR_API_KEY" "https://api.fxmacrodata.com/v1/announcements/usd/non_farm_payrolls"

Example response (abridged, illustrative values):

{
  "currency": "USD",
  "indicator": "non_farm_payrolls",
  "data": [
    {
      "date": "2026-08-01",
      "val": 142.0,
      "prior": 118.0,
      "announcement_datetime": 1788525000
    }
  ]
}

Fields that matter

• announcement_datetime: epoch seconds of the official release, the anchor for event studies.
• val and prior: the surprise inputs, typed as numbers.
• date: the reference period, separate from when it was published.

Versus a Myfxbook RSS item

The RSS item carries a title, link, minute-level pubDate, and an escaped HTML table holding previous, consensus, and actual as display strings. Turning that into numbers means HTML parsing and unit stripping.

Takeaway: Typed fields and a second-level timestamp remove the parsing layer that sits between a calendar feed and a trading rule.

For MetaTrader users, the MetaTrader 5 Python guide shows the same call driving an EA workflow, and the API reference lists every endpoint.

Where Myfxbook Is Genuinely Stronger

Myfxbook is one of the best-known retail forex communities for good reasons, and several of those reasons matter here:

• Free at every level a reader touches. The calendar, alerts, widget, and RSS cost nothing, and there is no key or trial to manage.
• Community sentiment. The community outlook, built from members' trading accounts, is available on the site, as a widget, and through the API. FXMacroData does not offer a retail positioning sentiment feed; its positioning data is CFTC COT.
• Account tracking and verification. Myfxbook's core product, tracked and verified trading accounts with gain and drawdown statistics, has no FXMacroData equivalent and is what its API is designed for.
• Breadth of the event list. More countries, holidays, and minor events than a 22-currency official-source API.
• Widgets for publishers. A large catalogue of free embeds, from the calendar to heat maps, correlation, and market hours.

If you are a discretionary trader who reads the calendar before the session and wants sentiment and account stats in the same place, Myfxbook may be all you need.

Where FXMacroData Is Stronger

FXMacroData is stronger as soon as a program, a team, or a paying audience is involved: documented endpoints, typed release rows, exact timestamps, published limits, and terms that fit automation.

FXMacroData pros

• Documented calendar and announcements API with OpenAPI, SSE, and SDKs.
• Second-level timestamps and a public release-speed record.
• Plans that cover automated and, with the add-on, redistributed use.
• COT, yields, commodities, press releases, and MCP alongside the calendar.

FXMacroData tradeoffs

• Non-USD data needs a paid plan after the 14-day trial.
• 22 currencies rather than a global event list.
• No retail sentiment or account-tracking features.

Myfxbook pros

• Free calendar with impact, consensus, actual, and reminders.
• Community outlook sentiment and account tracking.
• Wide free widget catalogue and RSS.

Myfxbook tradeoffs

• No economic calendar method in the public API.
• RSS for individual non-commercial use; API software should be free.
• Minute-level event times; no published latency figure.

Takeaway: Myfxbook wins the free reading experience; FXMacroData wins every requirement that starts with "my code needs to".

Decision Matrix

Recommendation

Keep using Myfxbook if the calendar is something you read. It is free, broad, and well integrated with the community outlook and account tracking that bring most people to the site. Nothing in this comparison suggests replacing it for that job.

Choose FXMacroData when the calendar has to become data: an EA that needs the Fed policy rate decision the second it lands, a backtest of GBP/USD after UK releases, a dashboard comparing ECB policy rate paths, or an alert on US unemployment that feeds an AUD/USD model. Start on the Always Free USD tier, check the release speed record, read the API reference, and compare plans when you need other currencies. For assistant-led research, the AI trading guides show the MCP route.

Bottom line: Myfxbook is a free calendar for reading, with no calendar API on its official documentation page and terms aimed at free, non-commercial use. FXMacroData is the documented, licensed FX macro API for the same events, with second-level timestamps and published pricing from $50/month.

Takeaway: Read on Myfxbook; build on FXMacroData.

Sources Checked

Competitor claims on this page come from Myfxbook's own public pages, checked in October 2026. Where Myfxbook does not publish a figure, this page says so rather than estimating it.

Myfxbook API

Method list, session rules, outlook limits, free-software condition.

View source

Myfxbook calendar

Columns, filters, time zones, CSV/XML export, real-time description.

View source

Myfxbook widgets and RSS

Calendar widget description and terms checkbox; RSS non-commercial wording.

Widgets · RSS

Myfxbook help and terms

Calendar features, event detail pages, and reproduction clause.

Help · Terms

FXMacroData

Plans, limits, endpoints, and the measured release-speed record.

Pricing · Release speed

Takeaway: Every Myfxbook limitation cited here is stated on, or absent from, Myfxbook's own official pages.

Related Reading

• FXMacroData vs Forex Factory: the other free retail calendar developers try to automate.
• FXMacroData vs Investing.com economic calendar: widget-first calendar versus API.
• FXMacroData vs FXStreet economic calendar API: a calendar vendor that does sell API access.
• Best economic indicator feeds for algo trading: the wider shortlist.