Plan: Professional and above · Credits: 1 per call
What you can use the calendar for
Know what prints this week and which of it matters. Compare an actual with the consensus that stood the day before, not the one that stood a month out. Line up a company’s earnings date against the macro releases around it.GET /v1/macro/calendar
Oldest first. The default window is today to 30 days ahead; passdate_gte and date_lte to look elsewhere, back to 2013.
string
default:"schedule"
schedule returns the calendar as it stands. snapshots returns the point-in-time history: one row per event per day it was captured.string
Two-letter ISO code.
EU is the euro area, GB the United Kingdom, WL world events.string
A fragment of the event name, matched ignoring spaces and punctuation:
CPI, Nonfarm, Interest Rate Decision.string
Earliest
scheduled_date, YYYY-MM-DD; defaults to today. date_lte sets the ceiling and defaults to today plus 30 days.integer
default:"100"
Rows per page, between 1 and 500. Page through with
cursor.One release is several rows
A far-out estimate is a placeholder
The snapshot history starts 2026-09-09
view=snapshots carries one row per event per snapshot_date, captured every day since 2026-09-09 for events from 21 days back to 30 days ahead. Nothing earlier exists and nothing earlier can be reconstructed: “what was consensus a week before the August 2026 CPI” is unanswerable, and stays so.
Key calendar fields
Schedule rows carrycountry, country_name, event, scheduled_date, scheduled_at (UTC, when the source gives a time), period_hint, unit, impact, previous, estimate, actual, and official_meeting, which is true for FOMC rows taken from the Fed’s own schedule (those carry no consensus). Snapshot rows carry country, event, scheduled_date, snapshot_date, estimate, previous and actual.
The response’s coverage block states schedule_from, snapshots_from and the snapshot window.