Get an upload's offset
HEAD/api/v1/uploads/:id
The tus offset request: answers with the upload's tus headers and no body, so a client resumes its transfer at Upload-Offset. The response is never cached.
Request
Responses
- 200
- 401
- 403
- 404
- 406
- 412
- 500
- 503
The upload's tus headers, without a body.
Response Headers
no-store, so no cache answers with an outdated offset.
Only for a ready upload: the RFC 9530 sha-256 digest of the stored content.
The tus protocol version. Every response of an upload operation carries it, Problem responses included, except a 406.
The upload's expiration time as an HTTP-date.
The upload's declared size in bytes.
The filename key with the upload's filename in base64.
The number of bytes the upload has received and stored, at which the next PATCH continues.
The authentication credential is invalid or has expired (unauthorized).
The request has no authentication credential, or the user is not allowed to use the API (forbidden).
The addressed resource does not exist, or no route matches the request method and path (not_found).
The request does not accept any representation the operation can produce (not_acceptable).
The Tus-Resumable request header names a tus protocol version other than 1.0.0 (unsupported_protocol_version). The request had no effect.
Response Headers
The tus protocol version. Every response of an upload operation carries it, Problem responses included, except a 406.
The tus protocol versions the server supports.
An unexpected server error occurred (internal_error).
The service is temporarily unavailable, for example while it restarts (service_unavailable). Retry the request later.