Introducing the Release Calendar Endpoint

The FXMacroData release calendar endpoint is now live. In a single API call you can retrieve every upcoming macro announcement across any supported currency — complete with the precise UTC timestamp, expected consensus, prior reading, and impact rating — so your models and dashboards always know what's coming before the market moves.

What's New

Until now, staying ahead of macro releases meant maintaining your own schedule of central bank meetings and statistical-office publication dates, pieced together from multiple sources. The release calendar endpoint changes that by exposing a single, structured feed of all upcoming announcements for a chosen currency — refreshed continuously as official dates are confirmed or revised.

Each entry in the calendar response carries:

Indicator name — the same slug used across all FXMacroData endpoints (e.g. cpi, policy_rate, unemployment_rate).
Announcement datetime — Unix timestamp at second-level precision, always in UTC, aligned with the moment of official publication.
Expected (consensus) — the market forecast in place ahead of the release.
Prior value — the previously published reading, including any revisions.
Revised flag — whether the prior value has been restated since its original publication.
Impact rating — a high / medium / low classification based on the indicator's historical market-moving tendency.

The calendar covers roughly 30 days of upcoming releases, sorted chronologically. For currencies like AUD, GBP, EUR, JPY, CAD, NZD, and CHF, a paid API key is required. USD data is available without authentication.

Why It Matters for Traders

Macro releases don't arrive on a neat regular schedule. Central banks announce meetings months in advance, but statistical offices like the ABS, ONS, or BLS publish CPI and jobs data on rolling schedules that shift slightly each cycle. Missing a release by even a few seconds introduces stale data into a live model — which, in thin pre-NFP liquidity, can mean a signal that fires on the wrong side.

The release calendar gives you two practical advantages:

Precision scheduling

Query the calendar once to get the exact announcement timestamp, then sleep your data fetcher until two seconds before the release fires. You make one targeted request per release instead of polling every few minutes — and you receive fresh data within seconds of official publication.

Risk window planning

Knowing that an RBA decision lands two days before the ABS unemployment print lets you plan position sizing across both risk windows in a single API call — rather than checking two separate feeds or calendar sources.

Beyond automation, the calendar is useful for manual trade preparation: scanning for overlapping high-impact releases across correlated pairs (AUD and NZD, for example) surfaces confluence risk that wouldn't be obvious from looking at a single indicator in isolation. See the AUD policy rate docs and the NZD policy rate docs for context on how those releases interact.

Practical Example: AUD Week Ahead

You're heading into a week that includes both the RBA cash rate decision and the Australian labour force survey. You want to pre-load the full schedule so your model can size positions appropriately across both event windows.

A single calendar call returns everything you need:

curl "https://fxmacrodata.com/api/v1/calendar?currency=aud&days_ahead=7&api_key=YOUR_API_KEY"

Response:

{
  "currency": "aud",
  "events": [
    {
      "indicator": "policy_rate",
      "announcement_datetime": "2026-03-18T03:30:00Z",
      "expected": 4.10,
      "prior": 4.35,
      "revised": null,
      "actual": null,
      "impact": "high"
    },
    {
      "indicator": "unemployment_rate",
      "announcement_datetime": "2026-03-20T00:30:00Z",
      "expected": 4.0,
      "prior": 4.1,
      "revised": null,
      "actual": null,
      "impact": "high"
    },
    {
      "indicator": "employment_change",
      "announcement_datetime": "2026-03-20T00:30:00Z",
      "expected": 22000,
      "prior": 44000,
      "revised": 41200,
      "actual": null,
      "impact": "high"
    }
  ]
}

The response surfaces three key facts in one call: the RBA is expected to cut by 25 basis points on Tuesday (prior 4.35, expected 4.10); the labour survey lands 45 hours later on Thursday; and the prior employment change has been revised downward from 44,000 to 41,200 — context that shifts the consensus framing for the unemployment print. A trader long AUD/USD can plan two distinct risk windows and decide whether to reduce exposure before the RBA and reassess, or hold through both events with defined stops, without consulting a separate economic calendar.

To explore the indicators surfaced in this example, see the AUD unemployment and AUD employment API docs.

Practical Example: USD High-Impact Scan

You're running a macro regime filter on EUR/USD and want to identify all high-impact USD releases in the next five days so you can suppress the model during event windows.

curl "https://fxmacrodata.com/api/v1/calendar?currency=usd&days_ahead=5&impact=high&api_key=YOUR_API_KEY"

Response:

{
  "currency": "usd",
  "events": [
    {
      "indicator": "cpi",
      "announcement_datetime": "2026-03-11T12:30:00Z",
      "expected": 2.9,
      "prior": 3.0,
      "revised": null,
      "actual": null,
      "impact": "high"
    },
    {
      "indicator": "nonfarm_payrolls",
      "announcement_datetime": "2026-03-14T12:30:00Z",
      "expected": 185000,
      "prior": 143000,
      "revised": 138500,
      "actual": null,
      "impact": "high"
    }
  ]
}

CPI lands on Wednesday and NFP follows on Friday. Both land at 12:30 UTC — the same time slot — making it straightforward to build a blanket suppression rule for that window without needing to hard-code specific dates. The revised NFP prior (138,500 versus the originally reported 143,000) is a detail that would typically require a separate data pull; here it arrives in the same calendar payload, letting you adjust the surprise-magnitude baseline before the Friday release.

For indicator-level field definitions, see the USD CPI docs and the USD nonfarm payrolls docs.

Get Started

The release calendar endpoint is available now. USD data requires no authentication. All other currencies require a paid API key — you can generate one from your account dashboard at fxmacrodata.com.

First steps

• Make a free test call: curl "https://fxmacrodata.com/api/v1/calendar?currency=usd"
• Explore the full field reference in the API documentation
• See how to build an event-driven scheduler in the scheduling how-to guide

If you're integrating the calendar into an existing data pipeline, the how to schedule indicator fetches with the release calendar guide walks through the full event-driven pattern in Python and JavaScript, including handling delayed releases, multi-currency threading, and retry logic.

— The FXMacroData Team

Securely Redirecting...