Introducing the Release Calendar Endpoint

The FXMacroData release calendar endpoint is now live. In one call you can retrieve upcoming release timestamps for a currency, filter down to one indicator when needed, and schedule follow-up announcement fetches against the exact publication second.

What's New

The production release-calendar route is /api/v1/calendar/{currency}, with an optional ?indicator=... filter. Instead of manually maintaining central-bank and statistics-office schedules, you can query a single production endpoint and receive release rows sorted by time.

Each row is built around two core fields:

• release - the canonical indicator slug used by the announcements endpoint, such as inflation, policy_rate, unemployment, or non_farm_payrolls
• announcement_datetime - the UTC publication timestamp used for scheduling and event studies

Some mixed-domain schedules also include additive routing metadata such as endpoint_family, endpoint_path, title, and schedule_status. Those fields help clients route the next request, but the timing workflow still starts with release plus announcement_datetime.

Why It Matters

Macro releases do not arrive on perfectly regular intervals. Central banks publish meeting calendars well in advance, while CPI, GDP, labor, and trade releases can move around month to month. If you are polling every five minutes, you either waste requests or accept avoidable latency.

Practical Example: AUD Policy Rate Scheduling

Suppose you only care about the next RBA decision. Filter the AUD calendar directly to the production policy_rate slug:

curl "https://fxmacrodata.com/api/v1/calendar/aud?indicator=policy_rate&api_key=YOUR_API_KEY"

Representative response:

{
  "currency": "AUD",
  "indicator": "policy_rate",
  "data": [
    {
      "announcement_datetime": 1773077400,
      "release": "policy_rate"
    }
  ]
}

That tells your scheduler exactly when to wake up and call the AUD policy rate announcement endpoint. The calendar tells you when the next event lands; the announcements endpoint tells you what printed once it lands.

Practical Example: USD Week-Ahead Scan

If you want the broader USD schedule, query the currency without an indicator filter and review the upcoming releases in chronological order.

curl "https://fxmacrodata.com/api/v1/calendar/usd"

Representative response:

{
  "currency": "USD",
  "indicator": null,
  "data": [
    {
      "announcement_datetime": 1773077400,
      "release": "inflation"
    },
    {
      "announcement_datetime": 1773682200,
      "release": "non_farm_payrolls"
    }
  ]
}

This is enough to build pre-release risk windows, suppress a model during known macro events, or queue follow-up fetches to the USD inflation and USD non-farm payrolls endpoints when those timestamps arrive.

How It Fits with the Announcements Endpoint

The release calendar is intentionally narrow: it tells you which release is next and when it is scheduled. Once the event is live, use /api/v1/announcements/{currency}/{indicator} to fetch the released historical series and read the newest row in the returned data array.

That division keeps scheduling logic clean. You query the calendar for timing, then query the announcements endpoint for values and announcement history.

Get Started

USD calendar access is public. Other supported currencies require an API key. Start with a free USD test call, then move to authenticated currency workflows once your scheduler is wired up.