Qdrant Cloud
POST /collections/{id}/points/search endpoint removal
Deprecated, no dateSubscribe to Qdrant CloudShare
Qdrant Cloud deprecated POST /collections/{id}/points/search without a shutdown date. Calls made to this endpoint eventually fail as the legacy search, recommend, and discover endpoints are removed. The unified query API introduced in version 1.10 supersedes these endpoints.
Calls it hits
POST /collections/{id}/points/search
What to use instead of these calls
Call POST /collections/{collection_name}/points/query, the Query API, before upgrading the cluster to Qdrant 1.19, which removed this endpoint.
In Qdrant Cloud's words
We've removed the legacy /search , /recommend , and /discover endpoints. The unified /query API superseded these endpoints in version 1.10 .
Facts
- API
- Qdrant Cloud
*.cloud.qdrant.io - Kind
- Endpoint removal
- Announced
- August 5, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Qdrant Cloud's own pages
Questions
When does this change take effect?
Qdrant Cloud deprecated POST /collections/{id}/points/search without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Qdrant Cloud 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.
More from Qdrant Cloud 4
-
No date
POST /collections/{id}/points/discover*Endpoint removal Deprecated, no date -
No date
POST /collections/{id}/points/recommend*Endpoint removal Deprecated, no date -
No date
POST /collections/{id}/points/search/batchEndpoint removal Deprecated, no date -
No date
POST /collections/{id}/points/search/groupsEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.