Census Data API
GET /data/* now requires an API key
Stopped workingSubscribe to Census Data APIShare
On May 11, 2026, the Census Bureau began requiring an API key for queries made to the Census Data API. This change impacts calls to GET /data/*, and any requests sent without a valid key now fail. The requirement applies to every user querying the API.
Calls it hits
GET /data/*
What to use instead of these calls
To update your integration, obtain a free key, activate it, and append key=<your key> to every query. Note that each deployment needs an API key that a person manually requests and activates.
Each deployment needs a Census API key that a person requests and activates.
In Census Data API's words
May 11, 2026 The Census Bureau now requires an API key for all queries made to the Census Data Application Programming Interface (API). This change affects every user of the Census Data API.
Facts
- API
- Census Data API
api.census.gov - Kind
- Behaviour change
- Announced
- May 11, 2026
- Takes effect
- May 11, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Census Data API's own pages
Questions
When does this change take effect?
Calls to GET /data/* on Census Data API stopped working on May 11, 2026.
What happens to calls after May 11, 2026?
They have failed since May 11, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.