/api/3/* → endpoint removal
Data.gov Catalog API
Deprecated, no date
The /api/3/* endpoints are deprecated without a shutdown date. The provider notes that the previous endpoint remains available in a read-only state for existing integrations, but requests will eventually fail. This change impacts all integrations making calls to paths under /api/3/*.
Calls it hits
/api/3/*
What to use instead of these calls
Migrate your calls to GET /search at the Data.gov Catalog API on api.gsa.gov/technology/datagov/v4/ using an api.data.gov key in the X-Api-Key header. Switching requires more than changing an identifier, as the new API requires this API key and returns a different response shape.
The new Catalog API needs an api.data.gov key and returns a different response shape.
In Data.gov Catalog API's words
Note: This API replaces the previous CKAN-based API. The prior endpoint remains available in a read-only state for existing integrations, but new development should use this API.
Facts
- API
- Data.gov Catalog API
catalog.data.gov - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Data.gov Catalog API's own pages
Questions
When does this change take effect?
Data.gov Catalog API deprecated /api/3/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Data.gov Catalog API has not given a shutdown date yet.
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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.