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/fetch \
-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
Returns the vectors you stored, by your own ids, with their metadata. Values come back at the index's own `dimension` — never at the wider width they may physically be stored in, which is an implementation detail you should never have to know about. A POST rather than a GET because the ids are yours and there may be a thousand of them. This does **not** count against `vector_queries_monthly`: fetching by id runs no nearest-neighbour search. Requires `vector.manage`, like `query`, because it returns your stored data rather than your usage.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
indexId (path) | string | Yes | The index's id. |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
ids | string[] | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
vectors | Vector[] | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429