# /api/3/* is deprecated

Data.gov Catalog API deprecated /api/3/* without giving a shutdown date yet.

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/*.

## What to use instead

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.

- API: Data.gov Catalog API (catalog.data.gov)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/api/3/*`
- Source: [Announcement](https://resources.data.gov/catalog-api/)
- Verified: October 27, 2026, against Data.gov Catalog API's own pages
- Page: https://www.okapi.bot/providers/data-gov-catalog-api/breaking-changes/api-3-is-deprecated/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent