Explore the response before integrating
Use a developer key to inspect a fixed historical sample. Start with its metadata, choose an included series, and run one bounded request.
The sample spans at most 90 days and is at least 90 days old when published. It does not contain live releases. Coverage is limited to eight major currencies, up to six series per currency and twelve retained records per series, including revisions. Announcement pages contain at most 25 rows; the calendar request uses your selected series.
Limits: 60 requests per minute, 1,000 per day, 10,000 per month and two concurrent requests. Live releases, other data families, source-value mode and point-in-time replay are outside this sample.
Review full data coverage · API documentation · Plans and access
1. Developer key
A verified email is required. Workspace keys are managed by an active owner or administrator.
Checking developer sample availability…
Sign in to manage a developer keyYour new key is shown below once. Save it securely before leaving this page.
The key stays in this page's memory. Examples use a placeholder, and your key is never added to the URL.
2. Inspect the sample
Load metadata to see the sample's exact dates and included series.
No request has been run.
Response appears here after a successful request.
Read the fields
- date / val
- The observation's period and value. Check the series unit and definition before comparing values.
- source / source_url
- Publisher attribution, where supplied.
- revisions
- Retained versions, where present. Retention does not establish a complete original-release history.
- published_after / published_by
- The observed publication interval, when captured. The scheduled time is a separate clock.
- available_at
- When the record was committed to the database. Publication latency is not measured when publication evidence is absent.
3. Run the same request in your client
Choose a sample request to generate an example.