POST
Complete a set of multipart uploads
Request · Guide: Upload files
Each upload is finalized on its own. One upload with a broken part list fails by itself and is returned with its own error — it never rolls back the uploads beside it, which for a bulk transfer means hundreds of megabytes of finished work are never discarded because of one bad part list. Retry just the upload that failed.Returns 201 when every upload was finalized, and 207 when some were and some were not. Inspect completed, failed and each result’s success either way.Sending the same Idempotency-Key again within 24h replays the original per-upload results and queues nothing for processing a second time.The input should contain:
  • batchId: (optional) the batch id from the initiate, echoed back for correlation
  • uploads: each with the id and key from the initiate and the full parts list

Authorizations

x-api-key
string
header
required

API key for authentication

Headers

Idempotency-Key
string

Optional opaque key (max 255 chars, UUIDv4 recommended) making this request idempotent for 24h: a retry with the same key and body replays the original response with Idempotent-Replayed: true.

Body

application/json
uploads
object[]
required

Uploads to finalize, at most 25 per request. Each upload is finalized independently — one broken part list never rolls back its siblings.

Required array length: 1 - 25 elements
batchId
string

The batchId returned by the batch initiate. Optional, and echoed back on the response for correlation; uploads are finalized by their own id and key.

Example:

"batch_01JA1ZC7S9V0F4C6H2M8QK3R7T"

Response

Every upload in the batch was finalized