Tracked core API
Use tracked indicator slugs when you need stable public JSON for the core library that powers the site, including the small committed global slice.
Tracked slugsPublic JSONRelease context
Data platform
API & data access
Public JSON, export links, and broader source-discovery routes in one place for apps, analysts, and research workflows.
Use it by job
Three public data surfaces
Connected-source discovery
Use the wider discovery routes when the tracked library is too narrow and the job shifts to World Bank, IMF, or deeper provider search.
World BankIMFResearch lanes
Downloads and monitoring
Use the file exports and health route when the job is integration, monitoring, or recurring pull-based workflows.
CSVJSONHealth checks
Endpoint families
Live route patterns
These are the public route families that already exist. Start with the tracked slug API for stable U.S. core series, then use connected-source discovery when you need wider country or multilateral coverage.
The tracked library route now supports lightweight filters like scope=global, starter=true, source=worldbank, and category=Growth.
Tracked indicator endpoints
Use the slug-based routes when you need page metadata, chart history, downloads, or release framing for one public series.
GET /api/indicators/libraryGET /api/indicators/library?scope=globalGET /api/indicators/library?scope=global&starter=trueGET /api/indicators/:slugGET /api/indicators/:slug/observationsGET /api/indicators/:slug/downloadGET /api/indicators/:slug/download/jsonConnected-source research endpoints
Use the search and preview endpoints when country or multilateral coverage matters more than the tracked U.S. starter library.
GET /api/indicator-import/search?provider=worldbank&q=gdp%20growthGET /api/indicator-import/search?provider=imf&q=inflationGET /api/indicator-import/preview?provider=fred&seriesId=GDPC1Timing, news, and monitoring endpoints
Use these routes when the job is release timing, macro-news joins, or uptime checks instead of one series history.
GET /api/calendar/releasesGET /api/newsGET /api/healthQuick starts
Start with one concrete path
Build against a tracked slug
Best when you already know the public series and want stable JSON for one core macro indicator.
GET /api/indicators/headline-cpi/observationsPull the tracked global starter
Best when you want the committed non-U.S. starter slice without opening the wider research and discovery routes.
GET /api/indicators/library?scope=global&starter=trueSearch broader multilateral coverage
Best when the question is country-level or multilateral and the tracked U.S. library is no longer enough.
GET /api/indicator-import/search?provider=worldbank&q=India%20GDP%20growthExport or monitor
Best when you need a file download, forecast output, or a lightweight health endpoint for infrastructure checks.
GET /api/healthPlatform reading order
Start with a tracked slug when you need stable public JSON for one core macro series.
Use the tracked global starter on the indicators explorer when you need a few committed non-U.S. series before moving into broader provider search.
Use connected-source search when the job changes from U.S. core tracking to country, multilateral, or provider-native discovery.
Use downloads when you need a file, and use /api/health when the job is uptime monitoring rather than content.
Boundaries
Current scope and limits
Public read-heavy routes are site-powered JSON endpoints, not a separate account-key developer product yet.
The tracked library route supports public filter params such as scope, starter, source, category, and slugs for stable pull-based workflows.
Connected-source search and preview routes are best treated as research and discovery surfaces, especially for attribution-bound or review-lane providers.
Indicator downloads, exports, and API responses still inherit source, attribution, and research-lane boundaries.
User-specific flows such as alerts, watchlists, and delivery status remain dynamic account surfaces, not public cacheable feeds.
Monitoring
Use the health route for uptime checks
The health route is the correct probe target for uptime monitoring. Do not use a heavier public page when the job is platform status.
GET /api/health