Upload a chunk
POST/:workspace/media/chunked/:uploadUuid/upload
Step 2 of the chunked upload flow. Uploads a single chunk, identified by a zero-based chunk_index between 0 and total_chunks - 1. Chunks may be sent in any order — and in parallel — because they are reassembled in chunk_index order when the upload is completed.
Each chunk must be no larger than the chunk_size returned by the initiate step.
The upload session is identified by the uploadUuid in the URL: the upload_session field is filled in by the server from that URL, and any value you send for it in the request body is ignored.
Request
Responses
- 200
- 401
- 403
- 404
- 422
Chunk stored. The response shape depends on where media is stored: either {chunk_index, size} or {chunk_index, part_number}.
The bearer token is missing, malformed, unknown, or expired.
The token is valid, but the user it belongs to may not perform this action:
- they are not a member of the
{workspace}in the path; or - their workspace role is too low for this endpoint (write routes require Admin or Member); or
- for
/panelendpoints, they are not a platform administrator.
The {workspace} UUID in the path does not match any workspace.
Validation failed. Only one error key is ever returned, since validation stops at the first failure. A uploadUuid that is unknown, expired, or belongs to another workspace or user is reported here as a required-field error on upload_session, because the server can only fill that field in from the URL when the session is one you may use.