Official US Economic Release Calendar API

Unofficial independent tool. It is not affiliated with, sponsored by, or endorsed by the U.S. Bureau of Labor Statistics, U.S. Census Bureau, U.S. Bureau of Economic Analysis, or Board of Governors of the Federal Reserve System.

Turn the official BLS, Census Bureau, BEA, and Federal Reserve schedules into one bounded, normalized dataset for alerts, calendars, agents, spreadsheets, and research pipelines. The Actor reads the BLS-published iCalendar feed, the Census-published economic-indicator calendar, BEA machine-readable release-date feed, and Federal Reserve calendar JSON directly. It does not scrape a third-party economic calendar, invent consensus estimates, or resell proprietary actual-value data.

What does the official macro calendar return?

Each row includes a deterministic event ID, source agencies, official title, scheduled UTC timestamp, Eastern date and time, period covered when Census supplies one, source identity, official source links, retrieval timestamp, and a transparent major or standard label. The major label is a title-based convenience filter for widely followed labor, inflation, trade, housing, productivity, and retail releases. It is not an investment recommendation or a claim about future market impact. Major releases are the default; set majorOnly=false when daily and weekly Federal Reserve statistical series are also required.

The output schema is stable and documented for JSON, CSV, Excel, Apify API, webhook, and MCP or AI-agent use. Event times are interpreted in America/New_York, including daylight-saving transitions, and also emitted as ISO 8601 UTC timestamps.

Example

Fetch the next 30 days of major releases from all four agencies:

{
  "startDate": "",
  "endDate": "",
  "daysAhead": 30,
  "agencies": ["BLS", "CENSUS", "BEA", "FED"],
  "search": "",
  "majorOnly": true,
  "maxItems": 200
}

Use explicit startDate and endDate values for reproducible historical or forward schedule snapshots. Search is case-insensitive and applies only to the official release title. The date range is inclusive in Eastern time. Every run has bounded agency, date, query, and record inputs, so scheduled jobs cannot silently turn into an unbounded crawl.

Primary-source behavior

The BLS feed provides persistent event UIDs and Eastern release times. The Census calendar supplies indicator pages, scheduled dates and times, and periods covered. BEA provides ISO 8601 release dates for GDP, personal income, trade, international accounts, and related releases. The Federal Reserve feed is restricted to timed statistical releases, FOMC events, and Beige Book releases; speeches, testimony, conferences, generic events, and rows without a scheduled time are excluded. Identical normalized titles at the same timestamp are merged across agencies with every supporting source retained, so a joint BEA/Census release is not returned or charged twice. Other rows are deduplicated by source identity. If one configured agency is temporarily unavailable but another succeeds, the run returns the available official records. It fails clearly when every configured source fails, rather than returning a misleading empty success.

Government agencies can revise or postpone release schedules. Treat every row as a timestamped schedule observation, not a permanent guarantee. Schedule a fresh run shortly before a release if timing is operationally important, and retain retrieved_at_utc for auditability. The Actor does not return released values, surprise calculations, forecasts, trading signals, or consensus estimates.

Pricing

The first 10 returned records in each run are free. Each additional official_macro_release costs $0.005. There is no start fee. The launch uses Pay per event + usage, so Apify platform usage is billed separately to the account running the Actor, including runs that return only free rows. maxItems hard-caps both output volume and possible paid events.

Responsible use and support

This product repackages publicly available schedule metadata for convenience; the linked government pages remain authoritative. Users are responsible for checking revisions, applicable terms, and the fitness of the data for their own alerts or automation. For a reproducible parsing or timing issue, open the Actor's Apify Issues tab with the run ID, agency, event ID, and source URL.