hosting

POST /v1/vector/indexes/{indexId}/vectors/delete

Delete vectors by id.

All hosting endpoints

Authentication

Send an API key as a bearer token. The key must carry the vector.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/vector/indexes/{indexId}/vectors/delete \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "ids": <string[]> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Removes vectors by your own ids. A POST rather than a DELETE with a body: a body on DELETE is permitted by the RFC and dropped by enough proxies that it is not a safe contract to sell. Requires `vector.manage`.

Parameters

NameTypeRequiredWhat it is
indexId (path)stringYesThe index's id.

Request body

NameTypeRequiredWhat it is
idsstring[]Yes

Response

NameTypeRequiredWhat it is
deletedintegerYes

Errors this endpoint can return

401 · 403 · 404 · 422 · 429