Qdrant API
- REST API
Vendor coverage
Vector databases sit in the hot path of AI features, and their APIs move at AI-ecosystem speed. Detektu diffs Qdrant's published OpenAPI contract so a changed search parameter or response shape is a finding, not a broken retrieval pipeline.
Last checked Oct 20, 2026, 3:26 PMLast change detected Oct 5, 2026, 12:28 PM
Detected changes
Every entry is a change Detektu detected in Qdrant's published contracts, with exact before/after evidence on its page.
openapi:GET /telemetry::response.200.application.json.result.collections.collections.items.openapi:GET /telemetry::response.200.application.json.result.collections.collections.items.openapi:PUT /collections/{}::request.application.json.vectors.anyOf[subschema-#2].additionalProperties.sizeopenapi:PUT /collections/{}::request.application.json.vectors.anyOf[#.components.schemas.VectorParams].sizeCoverage
Official products and contracts checked for changes.
Change model
The release patterns that shape your integration risk.
Qdrant publishes an OpenAPI contract for its REST API and iterates quickly: new query capabilities, extended filter syntax, evolving collection settings. Teams typically pin a client version and forget that the server contract underneath keeps moving.
Detektu reports each contract revision with exact coordinates, so changes to the points and search endpoints your retrieval code calls escalate, while new capabilities you don't use stay informational.
Monitored for you
Choose the operations and fields your services use. Detektu matches Qdrant findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.