completeUpload method

The request completes multipart upload.

When receiving the request, Object Storage:

  • Combines the parts obtained during the upload in the order of their numbering to form a target object.
  • Deletes the upload ID, which means that any subsequent requests with that ID will return the NoSuchUpload error.

When completing the upload, the client must provide the list of the parts it sent. Each part's description must contain the ETag which the client receives in response to each uploaded part. See the section uploadPart method.

The operation may take several minutes, depending on the object size and the number of parts.

If the request failed, the client app must be ready to repeat the request.


POST /{bucket}/{key}?uploadId=UploadId HTTP/1.1

Path parameters

Parameter Description
bucket Name of the bucket.
key Object key.

Query parameters

Parameter Description
uploadId ID of the multipart upload returned by Object Storage at the start.


In a request, use the necessary common request headers.

Data schema

The list of parts of a multipart upload is passed as an XML file in the following format:

Tag Description
CompleteMultipartUpload Data in the request.

Path: /CompleteMultipartUpload.
Part Data about the object's uploaded part.

Path: /CompleteMultipartUpload/Part.
PartNumber Part number.

A unique identifier that determines the part's position among the other parts in the upload.

Path: /CompleteMultipartUpload/Part/PartNumber.
ETag ID that the client received from Object Storage in response to a part's upload.

Path: /CompleteMultipartUpload/Part/ETag.



A response can only contain common response headers.

Response codes

For a list of possible responses, see Responses.

Additionally, Object Storage may return errors described in the table below.

Error Description HTTP code
NoSuchUpload The specified upload does not exist. The specified upload ID might be incorrect or the upload was completed or deleted. 404 Not Found
InvalidPart Some of the specified parts not found.

Possible causes:
- The parts have not been uploaded.
- The passed ETag does not match the saved one.
400 Bad Request
InvalidPartOrder The list of parts was not in ascending order.

The list must be sorted by part number in ascending order.
400 Bad Request

A successful response contains additional data in XML format with the schema described below.

Data schema

<CompleteMultipartUploadResult xmlns="">
Tag Description
CompleteMultipartUploadResult Response data.

Path: /CompleteMultipartUploadResult.
Location URI of the object created as a result of uploading.

Path: /CompleteMultipartUploadResult/Location.
Bucket Name of the bucket where the object is located.

Path: /CompleteMultipartUploadResult/Bucket.
Key Key of the created object.

Path: /CompleteMultipartUploadResult/Key.
ETag Hash value of the object.

ETag may or may not be an MD5 hash.

Path: /CompleteMultipartUploadResult/ETag.