Kagi
GET /api/v0/search endpoint removal
Deprecated, no dateSubscribe to KagiShare
Kagi deprecated GET /api/v0/search without giving a shutdown date yet.
Calls it hits
GET /api/v0/search
What to use instead of these calls
Call POST https://kagi.com/api/v1/search with a JSON body {"query": "..."} and Authorization: Bearer <API key>; the response shape changes (see the v1 OpenAPI spec).
The v1 Search API may need a new API key and access, and answers in another shape.
In Kagi's words
The legacy v0 Search API is deprecated
Facts
- API
- Kagi
kagi.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Kagi's own pages
Questions
When does this change take effect?
Kagi deprecated GET /api/v0/search without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Kagi 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.