Database endpoints
Delete a vector
Deletes one vector from a vector table by id; deleting an id that does not exist still succeeds with deleted set to false.
DELETE /v1/tenants/{tenant}/vector/{table}/{vec_id}
- Select collection and vector IDCheck the index type and optional repair setting.
- Request vector removalDelete that vector from the collection.
- Inspect the deleted flagDistinguish a removal from an already missing vector.
Before you start
Use your database bearer token.
Use the collection and vector ID you intend to remove.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
table | string | Required |
vec_id | string | Required |
Query parameters
| Field | Type | Required |
|---|---|---|
index | string | Optional |
repair | boolean | Optional |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
deleted is false when the vector was already absent. That is still a successful removal request; it is not evidence that a vector existed before the call.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 409 | Resolve the conflict before retrying. |
| 429 | Honor Retry-After when present; back off. |
| 503 | Honor Retry-After when present; check write outcomes. |