An economic calendar API
for scheduled and past releases.

What an event contains

Values are decimal strings as the source publishes them, so a reading of 2.84 for a year-over-year inflation rate means 2.84%. Read the release name for the unit; the unit field is often unknown because the source does not label units. A null value means not yet published or not supplied, never zero.

What the calendar is, and what it is not

This is a release calendar: when each report comes out and what it said. For the numbers as time series, use economic series and observations: Federal Reserve and U.S. Treasury rates, inflation and labor data, government bond yields of about 60 countries, and annual World Bank indicators such as GDP. The calendar source links no event to a series, so series_id is null on every event.

scheduled_at is the scheduled time in UTC, and release_date is its UTC date, so a release at 08:30 in Tokyo falls on the previous UTC day. The source does not report the instant a figure actually came out, a revised previous value or an importance rating: released_at and the value of revised_previous are always null, importance is always unknown, and there is no importance filter. Public holidays that the source calendar lists are left out.

How far back and how far ahead

Upcoming releases appear about seven days ahead. The source calendar begins in 2020 and is being backfilled from the present backwards; on October 3, 2026 the coverage endpoint reported history from 2026-09-08. Check the current range with GET /v1/datasets/economic.events/coverage, which reports history_from and history_to.

Filtering

• countries: comma-separated two-letter codes such as US
• from, to: an inclusive release_date range; from equal to to selects one day
• order: asc (default) or desc on release_date
• as_of, known_from, known_to: point-in-time and revision filters

curl 'https://api.ohlc.io/v1/economic/events?from=2026-10-01&to=2026-10-01&limit=100' \
  -H "Authorization: Bearer $OHLC_API_KEY"

Revisions

Many releases revise the prior period. previous is the prior figure as the calendar listed it before the release. revised_previous is reserved for the revised figure, which the current source does not publish, so its value is null. To see how an event changed, compare as_of cutoffs before and after the release.

Point in time

Because events change as the week goes on (forecasts update, actuals arrive, earlier figures get revised), as_of lets you read the calendar exactly as it stood at the end of a past UTC day. That is useful for testing how a strategy would have reacted to a release using only what was known before it.

Common uses

• Showing the coming week's releases on a dashboard or in a newsletter
• Flagging days with major U.S. reports before placing orders
• Comparing actual figures with forecasts after each release
• Pairing release dates with daily price moves to study market reactions

Plans

The economic calendar needs the economic.read capability, included on Pro, Commercial and Scale. Each request costs 5 credits, regardless of how many events it returns.

curl 'https://api.ohlc.io/v1/economic/events?countries=US&from=2026-10-05&to=2026-10-09' \
  -H "Authorization: Bearer $OHLC_API_KEY"

{
  "data": [
    {
      "id": "record_2234ccae5971c2ec1f85f2da874d4c7b90d05163664e4fc1b7ec583d1b0c59d6",
      "series_id": null,
      "name": "Michigan 5 Year Inflation Expectations",
      "country_code": "US",
      "release_date": "2026-10-09",
      "scheduled_at": "2026-10-09T14:00:00.000000Z",
      "released_at": null,
      "reference_period": "Oct",
      "importance": "unknown",
      "actual": { "value": null, "unit": "unknown", "currency_code": null },
      "forecast": { "value": "3.5", "unit": "unknown", "currency_code": null },
      "previous": { "value": "3.4", "unit": "unknown", "currency_code": null },
      "revised_previous": { "value": null, "unit": "unknown", "currency_code": null },
      "status": "scheduled"
    }
  ],
  "meta": {
    "timezone": "UTC",
    "as_of": "2026-10-03T15:05:11Z",
    "next_cursor": null,
    "coverage": { "status": "partial", "reason": "Coverage is partial for the entitled query scope." }
  }
}