For developers, newsrooms and research teams

Economic data API, from the official release to your workflow.

Track inflation, employment, GDP and central-bank decisions without building a separate collector for every agency. Econfeed keeps the published file, checks the data and preserves its revisions.

Econfeed is in early access. Public API access and self-service accounts are not open yet. The examples below describe the implemented interface, not an endpoint you can use without access.

Request early access

Real-time economic releases: choose how they arrive.

REST API
Fetch series, observations and release history. Use it for dashboards, scheduled analysis and catching up after an interruption.
WebSocket or server-sent events
Keep a connection open for release events. Filter by source, country or series rather than polling every indicator.
Signed webhooks
Receive events at your own endpoint. Use them to trigger an internal alert, refresh a chart or start a reporting workflow.

Python, JavaScript and R clients support data workflows. The important distinction is between when an agency publishes, when the API has the data and when an event reaches a consumer. These are not the same timestamp.

Delivery speed varies by agency and release. A value that fails a check is held back; an agency-imposed delay still applies. Inspect measured delivery times and misses rather than treating a speed claim as a guarantee.

Economic calendar API: schedules are not released values.

Use the calendar to plan around upcoming publications. Entries carry the scheduled time in UTC, the agency's local time and time zone, and whether a date is announced, provisional or rule-based. The reference period identifies the month or quarter the release covers when the agency supplies it.

GET /v1/calendar?country=US&kind=release
GET /v1/calendar/changes?source=us_bls_cpi

Filter by country, source, event kind or importance. The change log records added dates, reschedules, confirmations and cancellations. A calendar entry tells you when to expect a release; use the release and observation endpoints for the published data.

Browse release schedules by country, or check the coverage matrix before choosing the sources for your application.

Keep the first print and the later revision.

A revised historical series can answer a different question from the data available on the day. Econfeed keeps versions and the time each value became known. Use as_of to request the version known at a chosen time, or request vintages to examine revisions.

GET /v1/series/US.CPI.ALL.SA/observations?start=2024-01&as_of=2026-10-01T12:00:00Z

This is useful for point-in-time research and checking a published report. Vintage coverage depends on the source and retained history: it is not a claim that every historical first print can be reconstructed. Official values remain separate from computed changes, and each stored value traces back to an archived agency file.

Read the API compatibility and deprecation policy before planning an integration.

What to check before integrating.

  • Coverage: check the countries, indicators and release frequencies you actually need, not just a total source count.
  • Timing: compare measured releases, sample sizes and misses. No fixed latency or uptime guarantee is offered here.
  • Rights: review each source's licence and attribution. Access to an API does not grant unrestricted redistribution.
  • Access: tell us which releases matter, whether you need historical vintages or live events, and how you plan to use the data.

Early access is free. There are no public paid plans on this site; any price is agreed in writing before billing. Tell us about your workflow.