What you get#
Onekey exposes FRED as 4 endpoints behind one API key: 1 endpoint return one record (data is an object) and 3 endpoints return a list (data is an array). Every answer uses the same envelope (success, data, metadata, error), the cost is reported in metadata.credits_charged, and fields are mapped onto the unified schema so the code you write for FRED also works for the rest of the finance & markets category.
Endpoints#
| Endpoint | What it does | Parameters | Credits | Status |
|---|---|---|---|---|
category_series | Series in a FRED category. | category_id*, limit | 5 | beta |
observations | FRED observations (latest first). | series_id*, limit | 5 | beta |
search | Search FRED series by text. | q*, limit | 5 | beta |
series | FRED series metadata (title, units, frequency). | series_id* | 1 | beta |
A * marks a required parameter. Each endpoint name links to its reference page with the full parameter table, caching window and a recorded response.
Make a request#
This calls fred.series (1 credit, beta). Replace YOUR_API_KEY with your key; sign up, no card. 1,000 free credits cover the open-platform endpoints. Hard-to-reach platforms (X, TikTok, Instagram, Reddit, and others marked on their page) need a verified email and a purchased pack.
curl "https://api.onekey.dev/v1/fred/series?series_id=GDP" \
-H "x-api-key: YOUR_API_KEY"Fields you get back#
These unified fields come back from FRED, with the same names as on every other platform. The count is how many of its 4 mapped endpoints return the field; a field the source lacks is null, never missing. 2 platform-specific fields (ext.<name>) come on top, documented on each endpoint page.
| Field | Type | Endpoints |
|---|---|---|
entity.category | string | 3 |
entity.id | string | 3 |
entity.name | string | 3 |
entity.date | ISO 8601 date | 2 |
entity.stats.popularity | number | 2 |
entity.createdAt | ISO 8601 date | 1 |
entity.description | string | 1 |
The full schema is in Unified schema.
Pricing#
FRED calls cost 1 to 5 credits, flat per endpoint. Free when served from cache (0.2 credit for a cached response over 100 KB). Invalid, failed or not-found calls are not charged. See pricing for credit packs.