Trading Economics API: Pricing, Limits & FXMacroData Compared

If you are choosing between FXMacroData and Trading Economics, the real decision is not "which API has more data?" It is whether you need a broad global macro database, or a focused FX macro workflow that gets a trader or quant team from scheduled release to pair-level decision faster.

Trading Economics remains the broader product. Its public site presents macro, market, forecast, Excel, calendar, and API surfaces across 196 countries and 20 million indicators. FXMacroData is intentionally narrower: lower-cost, FX-specific macro data, release timestamps that declare whether they were captured or derived, pair dashboards, release-calendar context, COT, bond yields, commodities, press releases, exports, widgets, and AI/MCP-ready access.

Decision snapshot

Choose Trading Economics when

You need very broad country coverage, general macro lookup, market data, forecasts, Excel workflows, and a large cross-country economic database.

Choose FXMacroData when

You trade or model FX and need release timing, official-source macro history, pair context, dashboards, API access, and automation-ready data.

Fast verdict

Trading Economics wins on breadth. FXMacroData is the better fit for FX-specific, release-aware, developer-led workflows.

How We Compare The Platforms

The most useful comparison is not a generic feature count. It is whether the platform solves the job an FX team actually has: identify a release, trust the data, understand the pair context, and move the result into a model, dashboard, or agent workflow.

01 / Price

Can a serious workflow be tested without enterprise procurement?

02 / Breadth

How broad is the country, indicator, and market-data universe?

03 / Timing

Does the data support release-aware backtests and alerts?

04 / Workflow

How quickly can a macro release become pair-level analysis?

05 / API

Are the data surfaces clean enough for notebooks, apps, and alerts?

06 / Agents

Can the data be cited and used safely in AI-assisted workflows?

Takeaway: the winner changes by job. Trading Economics is stronger when breadth matters most; FXMacroData is stronger when the workflow is release-aware, FX-specific, and automation-led.

Pricing At A Glance

Price should be visible early because the entry gap is large. FXMacroData's public pricing page lists Individual at $50/month with a 14-day trial, Business for companies and teams at $250/month, an Always Free USD tier, and Enterprise by custom agreement. The Trading Economics API pricing page lists Standard at $199/month (500 API requests/month) and Professional at $399/month (5,000 API requests/month), with 25% off billed yearly (about $149 and $299 per month) and Enterprise custom pricing. There is no free API tier; one-week paid trials are capped at 100 requests. The economic calendar API and streaming are Enterprise-only: neither Standard nor Professional includes calendar data through the API.

Published monthly API pricing

Public pages checked October 2026; monthly billing shown, Trading Economics offers 25% off billed yearly.

$50

FXMacroData entry

FXMacroData Individual $50

Trading Economics Standard* $199

Trading Economics Professional* $399

4x lower entry price

FXMacroData Individual ($50, 1,000,000 requests/month) versus Trading Economics Standard ($199, 500 requests/month, no calendar API).

Different tradeoff

Trading Economics buys breadth; FXMacroData buys FX workflow fit.

* Trading Economics pricing retrieved from its public API pricing page in October 2026. Public pricing can change. FXMacroData pricing retrieved from the public subscription page in October 2026.

Evidence Checked For This Comparison

Comparison articles are only useful if the reader can see what was checked. The claims in this page are grounded in public pricing, documentation, and product pages checked in October 2026.

FXMacroData pricing

Always Free, Individual, Business, trial, Commercial Redistribution, and Enterprise plan language.

View pricing

Trading Economics pricing

Standard, Professional, and Enterprise API pricing, request caps, and calendar availability.

View pricing

Trading Economics docs

API overview, developer docs, rate-limit and row-limit notes.

View docs

FXMacroData docs

REST API, data docs, release-calendar and workflow surfaces.

View documentation

Audit note: public pricing and feature pages can change. For future refreshes, re-check these pages before reusing the comparison numbers.

Side-By-Side Comparison

Coverage: Breadth Versus FX Workflow Depth

Trading Economics has the broader universe. Its public pages describe 20 million indicators across 196 countries, plus currencies, commodities, bonds, indexes, financials, forecasts, Excel, and API access. That breadth is valuable if your work is cross-country macro research or general economic lookup.

FXMacroData is deliberately tighter. It is built around what FX users do repeatedly: prepare for a release, understand the pair context, compare policy and inflation differentials, monitor bond yields, check COT positioning, scan central-bank communication, and move the result into a dashboard, API request, export, widget, or agent workflow.

Trading Economics

Broad macro database

Country breadthVery high

Market data scopeWide

FX workflow packagingGeneral

FXMacroData

FX workflow layer

Release-to-pair contextHigh

Dashboard/API activationHigh

Global breadthFocused

Read the chart this way: Trading Economics wins when breadth is the product. FXMacroData wins when the job is turning a macro release into pair-level analysis, API output, or automation.

Why Timestamp Precision Matters For FX

A date-level macro history is enough for a long-run chart. It is weaker for release-aware trading, post-event attribution, and systematic FX research. If you are studying how EUR/USD reacted to euro-area inflation or how USD/JPY moved after US payrolls, the timestamp is part of the dataset. FXMacroData releases are typically available within seconds of official publication, and that speed is measured publicly release by release.

Release-aware workflow

01 / Scheduled

08:30 release time

The calendar date alone is not enough for intraday FX research.

02 / Official

Actual, prior, forecast

The release needs values and source context in the same record.

03 / Timestamped

announcement_datetime

FXMacroData keeps the event anchor explicit for joins and audits.

04 / Activated

Backtest or alert

Pair-level reaction can be separated from pre-release drift.

Takeaway: a release-aware FX workflow needs the moment of the announcement, not only the calendar date.

Feature Fit Heatmap

Both products are serious. The difference is where each one is strongest. Trading Economics is broader across countries, indicators, market data, Excel, and forecasts. FXMacroData is stronger where the job is FX macro activation: release timing, pair dashboards, source-labelled data, workflow surfaces, and integration into trading or AI workflows.

Feature fit by use case

Use case FXMacroData Trading Economics

FX release timing Strong Calendar API: Enterprise

Global country breadth Focused Very broad

Pair dashboards Native General macro

Excel and broad exports Exports Strong

COT, yields, commodities, press releases FX packaged Broad data

Trading-platform onboarding Guided SDK/API

AI and agent readiness MCP + docs MCP server

Pros And Cons Review Notes

A good comparison should make the strengths and tradeoffs visible, not bury them in a table. Read these notes as the buyer-facing review summary: what each product is clearly good at, and where it is less likely to be the right fit.

FXMacroData pros

• $50/month entry price with a 14-day trial, plus an Always Free USD tier.
• Exact release timestamps for event studies and alerts.
• Release calendar API, FX pair dashboards, widgets, exports, and an MCP server built around timestamped official releases.

FXMacroData tradeoffs

• Narrower global country and indicator breadth by design.
• Less suited to general macro-terminal or Excel-first research teams.
• Best when the workflow is FX-specific rather than all-asset macro lookup.

Trading Economics pros

• Very broad country and indicator coverage.
• General macro database, forecasts, market data, and Excel workflows.
• Strong fit for cross-country economic research beyond FX.

Trading Economics tradeoffs

• Higher self-serve API entry price and no free API tier.
• Economic calendar API is Enterprise-only.
• Monthly request caps of 500 (Standard) or 5,000 (Professional).

Review takeaway: FXMacroData has the stronger product fit for price-sensitive FX teams that need release timing and automation. Trading Economics has the stronger fit when broad macro coverage is the main buying criterion.

What A Real FX Workflow Looks Like

Most FX workflows are not single endpoint workflows. A trader preparing for US CPI wants the release time, prior and forecast values, actual print, pair dashboard, rates context, positioning, and a way to push the data into a model, notebook, alert, or AI assistant. This is where FXMacroData's narrower scope becomes useful.

Example workflow: US CPI into EUR/USD research

Plan

Release calendar

Know the event time, currency, prior, and forecast.

Capture

Timestamp + values

Pull actual, prior, forecast, source, and announcement time.

Compare

EUR/USD context

Check pair dashboard, yields, policy, COT, and recent macro.

Act

Model or alert

Send the event into a notebook, webhook, API job, or agent.

Dashboard

Pair, yields, COT, commodities.

API

JSON records with event timestamps.

Agent

MCP and citable docs for AI workflows.

Product Surface: What The Reader Should Picture

FXMacroData is not just a raw endpoint catalogue. A practical setup can use dashboards for human review, API endpoints for models, exports for spreadsheets, widgets for distribution, and MCP/OpenAPI paths for agent workflows.

Release Calendar

Plan event risk before a release hits.

Pair Dashboard

Tie releases to the currency pair being traded.

API And Agents

REST OpenAPI MCP

Send official-source context into code, widgets, or MCP tools.

Takeaway: the product surface matters. A lower-cost API is more useful when the adjacent dashboard, export, and agent paths reduce setup friction.

API Example: The Data Field That Matters

The most important field for a release-aware FX workflow is often not the value itself, but the release timestamp attached to that value. A production request should send the API key in the X-API-Key header:

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

{
  "currency": "USD",
  "indicator": "inflation",
  "source": "BLS",
  "data": [
    {
      "date": "2026-05-31",
      "val": 4.2,
      "previous_value": 3.8,
      "announcement_datetime": 1781094600,
      "announcement_datetime_local": "2026-06-10T08:30:00-04:00",
      "source_url": "https://www.bls.gov/news.release/archives/cpi_06102026.htm"
    }
  ]
}

That structure is useful because it gives a model or analyst a clean event anchor. The release time can be joined to tick data, pair moves, dashboard notes, and post-release commentary.

Where Trading Economics Is Genuinely Stronger

This page should not pretend Trading Economics is weak. It is not. Trading Economics is a strong choice when the job needs:

• very broad country coverage across nearly every economy,
• a large general-purpose macro and market database,
• Excel-oriented workflows,
• forecasts and broad economic dashboards,
• SDKs and examples across common developer languages,
• macro context that extends beyond FX trading and release workflows.

If your team needs a wide macro library for dozens of countries and many asset classes, Trading Economics may be the better primary source. FXMacroData is not trying to replace that broad research use case.

Where FXMacroData Is Stronger For FX Teams

FXMacroData is stronger when the product needs to answer a narrower but more urgent question: what does this macro release mean for a currency pair, and how fast can I get the data into my workflow?

• Lower entry cost: $50/month Individual pricing makes it easier for traders, small teams, and independent developers to test a serious setup.
• Release-aware data: second-level announcement_datetime fields and a release calendar API on every paid plan support event studies and alerts.
• FX context: release calendar, pair dashboards, COT, bond yields, commodities, and press releases sit near the macro data.
• Developer activation: REST, OpenAPI, SSE streaming, widgets, exports, and MCP make the data easier to plug into trading and AI workflows.
• Less stitching: the reader does not have to assemble calendars, pair context, positioning, and dashboard views from unrelated systems.

Decision Matrix

Recommendation

Choose Trading Economics if your main problem is broad macro coverage across many countries, indicators, forecasts, market datasets, and spreadsheet workflows. It is the wider database and remains a strong general macro platform.

Choose FXMacroData if your main problem is FX macro execution: monitoring releases, storing precise timestamps, preparing for NFP or CPI, comparing pair context, using dashboards, pushing data into a model, and giving AI tools official-source macro context.

Bottom line: Trading Economics is the better broad macro database. FXMacroData is the better FX macro workflow product for traders, quant developers, and automation teams that care about cost, release timing, pair context, and faster integration.

Start with the Market Summary, check the Release Calendar, and review the API documentation before deciding whether the focused workflow matters more than broad country breadth.