Datadory notebook
Cdc Socrata Api App Token Data: Dataset Structure and Field Coverage
Datadory delivers cdc socrata api app token data covering comprehensive field definitions, entity mappings, and historical time series — structured for direct analytics and delivered on demand.
1,744 datasets. Pick your catch.
How do you register and send the token?
A concrete REITs-flavored example: to pull the NCHS Leading Causes of Death file (four-by-four ID bi63-dtpu) with a filter and a page size, request ` The same query without the parameter still works for moderate use - no integration key is required for that - it just runs through the shared anonymous pool where CDC/Socrata rate limits apply.
Which Data.CDC.gov datasets does a token unlock at volume?
The catalog's about 1,078 dataset resources break down in a way that matters for pipeline design: roughly 225 are NCHS-tagged, and those are the files senior-housing and skilled-nursing analysts lean on. Four verified examples with stable four-by-four IDs:
| Dataset (ID) | What it holds | Grain |
|---|---|---|
NCHS - Leading Causes of Death: United States (bi63-dtpu) | Death counts and age-adjusted death rates by 113 Selected Causes | State-year |
NCHS - Death rates and life expectancy at birth (w9j2-ggv5) | Mortality rates and life expectancy series, some reaching back to 1915 | National/state |
NCHS - VSRR Quarterly provisional estimates for selected birth indicators (76vv-a7x8) | Quarterly natality rates by demographic stratum, current to 2026 Q1 | Quarter x stratum |
Indicators of Health Insurance Coverage at the Time of Interview (jb9g-gnvr) | Coverage and access indicators | National and state |
How far can you push the anonymous endpoint before registering?
The thresholds are deliberately unpublished: Socrata judges “too many requests” case by case, which is why the honest answer is a workflow rule rather than a number. Anonymous traffic shares one pool per IP, so two jobs from the same box compete even when each alone looks modest.
There is also a discovery step people forget. The JS browse front end at data.cdc.gov/browse?category=NCHS does not expose results to plain HTTP fetches - and passing category=National Center for Health Statistics to the catalog API returned zero results during research, while q=NCHS returned the verified resultSetSize of 225. So the programmatic discovery call ` is part of every harvest, it consumes quota too, and it benefits from the same token as the row queries behind it.
How does the token interact with frozen vintages and de-duplication?
De-duplication matters too: several datasets share titles across vintages (multiple “Drug Poisoning Mortality by County” entries), so harvest code needs a rule keyed on data_updated_at to pick the live vintage. A token makes both checks cheap; it cannot make them unnecessary.
Why does this matter specifically for health care REITs analysis?
In this industry slice, CDC's portal is the demand-side layer beneath roughly 15-25 listed US names (WELL, VTR, ARE, DOC, OHI, CTRE). County- and state-level mortality, aging-related chronic disease prevalence and insurance coverage drive long-run utilization of senior housing, outpatient medical buildings and post-acute care - the assets on the REIT balance sheet.
Is the app token required, and are there alternatives?
Not required - recommended. The catalog itself states that Socrata API usage is subject to CDC/Socrata rate limits with an app token recommended for volume queries, and the platform terms reserve the right to change limits with notice. Treat the anonymous pool as fine for exploration and inadequate for scheduled production.
Alternatives inside the same industry slice:
Where to go next
Start with the pillar health care reits data guide for how the CDC layer fits the full 14-dataset stack, then go deeper on the two records this page leans on: the CDC Data.CDC.gov Open Data Portal profile and the CDC NCHS Data Browsing Collection bulk set. For the other side of the join, see the CMS Provider Data Catalog facility files, or the industry hub for the complete ranked list.
Pick up where this leaves off
Every one of these ships with sample rows before you commit to anything.
CDC Data.CDC.gov Open Data Portal
_113_cause_name · topic · topic_subgroup …+2 more
CDC NCHS Data Browsing Collection
_113_cause_name · topic · topic_subgroup …+1 more
CMS Provider Data Catalog
ccn · overall_rating · health_inspection_rating …+4 more
CMS Data Hub - Medicare & Medicaid Datasets
HCUP - Healthcare Cost and Utilization Project
PAY1 · HOSP_NIS · DISCWT
Want rows instead of a pitch? Name the datasets.
API, files, or your warehouse. Daily, weekly, or hourly.
Get a sampleQuestions worth asking
Do I need a CDC Socrata API app token to query Data.CDC.gov?
No. Moderate use works anonymously - no integration key is required. An app token is recommended for volume queries because unauthenticated requests share a per-IP throttling pool, while token-bearing requests get their own pool and are generally not throttled unless abusive. Throttled requests return HTTP 429.
How do I pass the app token on a SODA request?
Register a token in a Socrata profile, then send it with every call via the X-App-Token header (SODA 2.x/3.0) or the $$app_token query parameter. The same token covers row queries at /resource/<id>.json, metadata at /api/views/<id>.json and catalog search at /api/catalog/v1.