/api/* → version retirement
Censys Search API
Deprecated, no date
Censys has deprecated the Legacy Search API without a specific shutdown date, as part of a plan to decommission it in 2026. This change impacts calls to all /api/* endpoints on search.censys.io, which will eventually fail. The host data backend will be updated on March 31, 2026.
Calls it hits
/api/*
What to use instead of these calls
Transition to the Censys Platform API, using global data under /v3/global/ with a Platform personal access token. Moving requires more than swapping an identifier: you must create a Censys Platform account, obtain a new token, and rewrite your queries to use CenQL instead of the Legacy Search syntax.
The Platform API needs a Censys Platform account, a new token and rewritten queries (CenQL instead of the Legacy Search syntax).
In Censys Search API's words
As part of the plan to decommission Legacy Search (search.censys.io) in 2026, Censys will update its host data backend on March 31, 2026.
Facts
- API
- Censys Search API
search.censys.io - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Censys Search API's own pages
Questions
When does this change take effect?
Censys Search API deprecated /api/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Censys Search 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.