Status
GET /v1/status · public
How fresh each part of the data is, judged against the source's real release cadence, plus pipeline and API health. It powers the public status page. Cached for 60 seconds.
{
"success": true,
"modules": [
{ "module": "fixed-income", "last_date": "2026-09-24", "series_count": 49,
"observation_count": 27790, "frequency": "daily", "age_days": 0, "state": "fresh" },
{ "module": "alternate", "last_date": "2026-03-31", "series_count": 75,
"observation_count": 965, "frequency": "quarterly", "age_days": 177,
"state": "current", "awaiting_source": true }
],
"datasets": [
{ "dataset": "funds", "records": 1278386, "entities": 588, "first_date": "1996-02-11",
"last_date": "2026-09-21", "frequency": "daily", "age_days": 3, "state": "fresh" }
],
"jobs": [
{ "job_name": "derive_auctions", "last_status": "success",
"last_run_at": "2026-09-24T04:00:23Z", "last_rows": 0, "last_success_at": "2026-09-24T04:00:23Z" }
],
"ops": { "p95_ms": 62.5, "requests_24h": 16788, "availability_pct": 100.0 }
}
States
state |
Meaning |
|---|---|
fresh |
Up to date for its cadence |
current |
Older than usual, but awaiting_source: true: the pipeline is healthy and the source hasn't published the next period yet (common for quarterly and annual releases) |
delayed |
Behind its normal release lag |
stale |
Genuinely lagging or failing |
Thresholds follow each module's typical publication lag. For example, annual fiscal data is normally 15-18 months old at its freshest, so it isn't judged against a monthly standard.
datasets covers the entity tables: funds, securities, trade and auctions. ops reports API p95 latency, 24-hour request volume and availability.