startUpload method
Returns the ID that should be used in all subsequent operations for uploading objects.
If the object is to be stored with user-defined metadata, it should be passed in this request.
Request
POST /{bucket}/{key}?uploads HTTP/2
Path parameters
Parameter | Description |
---|---|
bucket |
Bucket name. |
key |
Object key. The object will be saved in Object Storage with the specified name. |
Query parameters
Parameter | Description |
---|---|
uploads |
Flag indicating the multipart upload operation. |
Headers
Use the necessary common request headers in requests.
You can also use the headers listed in the table below.
Header | Description |
---|---|
X-Amz-Meta-* |
Object user-defined metadata. Object Storage transforms all headers starting with X-Amz-Meta- as follows: X-Amz-Meta-foo-bar_baz → X-Amz-Meta-Foo-Bar_baz .Total user-defined header size must not exceed 2 KB. The size of user-defined data is determined as the length of the UTF-8 encoded string. The header names and their values are included when calculating the size. |
Response
Headers
Responses can only contain common response headers.
Response codes
For a list of possible responses, see Responses.
A successful response contains additional data in XML format with the schema described below.
Data schema
<InitiateMultipartUploadResult>
<Bucket>bucket-name</Bucket>
<Key>object-key</Key>
<UploadId>upload-id</UploadId>
</InitiateMultipartUploadResult>
Tag | Description |
---|---|
InitiateMultipartUploadResult |
Response root tag. Path: /InitiateMultipartUploadResult . |
Bucket |
Name of the bucket the object is uploaded to. Path: /InitiateMultipartUploadResult/Bucket . |
Key |
Key associated with the object after the upload is complete. Path: /InitiateMultipartUploadResult/Key . |
uploadId |
Upload ID. All subsequent upload operations must pass this ID to Object Storage. Path: /InitiateMultipartUploadResult/UploadId . |