Download document
A short-lived signed link to the file the customer originally uploaded.
- Authentication
- Bearer token
- Retries
- Safe to repeat
- Body
- None
- Version
- 2026-09-03
Returns the URL rather than the bytes. Proxying a download through the API holds a worker for as long as somebody's connection lasts, which is a poor use of a small container when the object store does this natively - and the signature is what enforces the tenant boundary, not the redirect.
404 rather than 204 when no original exists, because "this document has no stored source" and "no such document" are the same answer to a caller: there is nothing here to download. Documents added as pasted text or crawled URLs never had a source file, and documents uploaded before this shipped were not kept.
Path parameters#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Knowledge base endpoints#
Something unclear or missing? Tell us and we’ll fix it.