Append one checksummed bounded transfer chunk
PATCH/api/v1/uploads/:upload_id
The per-request chunk budget bounds memory and retry cost; it is not a whole-document limit. A successful response advances Upload-Offset only after the chunk is durable.
Request
Responses
- 204
- 400
- 401
- 403
- 409
- 412
- 413
- 415
- 421
- 460
- 503
Chunk durably appended; Upload-Offset is the next position
Response Headers
TUS protocol version 1.0.0
HTTP-date after which the session expires
Declared total byte length
Next durable byte offset
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request syntax, headers, body, or validated input is malformed or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request conflicts with the current resource, revision, lease, credential, or idempotency state
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The strong revision precondition is stale
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A configured streaming body or per-file size limit was exceeded. A transport-level rejection may omit the JSON body.
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The payload media type is not accepted for this operation, or the file's actual content type is unsupported
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The supplied chunk checksum did not match
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A required core dependency is unavailable; retry with bounded backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.