# Uploads Multipart Uploads into a Bucket ## CreateMultipartUpload > \

This operation initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests. You also include this upload ID in the final request to either complete or abort the multipart upload request.\

```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"CreateMultipartUploadOutput":{"type":"object","properties":{"Bucket":{"$ref":"#/components/schemas/BucketName"},"Key":{"$ref":"#/components/schemas/ObjectKey"},"UploadId":{"$ref":"#/components/schemas/MultipartUploadId"}}},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}},"ObjectKey":{"description":"The object key.","type":"string","minLength":1,"maxLength":1024},"MultipartUploadId":{"description":"ID of the multipart upload.","type":"string"}}},"paths":{"/{Bucket}/{Key}?uploads":{"post":{"tags":["Uploads"],"summary":"CreateMultipartUpload","operationId":"CreateMultipartUpload","description":"

This operation initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests. You also include this upload ID in the final request to either complete or abort the multipart upload request.

","responses":{"200":{"description":"Successful operation","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/CreateMultipartUploadOutput"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"Key","in":"path","required":true,"description":"Object key for which the multipart upload is to be initiated.","schema":{"type":"string","minLength":1}},{"name":"uploads","in":"query","required":true,"schema":{"type":"boolean","enum":[true]},"allowEmptyValue":true},{"name":"Cache-Control","in":"header","required":false,"description":"Specifies caching behavior along the request/reply chain.","schema":{"type":"string"}},{"name":"Content-Disposition","in":"header","required":false,"description":"Specifies presentational information for the object.","schema":{"type":"string"}},{"name":"Content-Encoding","in":"header","required":false,"description":"Specifies what content encodings have been applied to the object and thus what decoding mechanisms must be applied to obtain the media-type referenced by the Content-Type header field.","schema":{"type":"string"}},{"name":"Content-Type","in":"header","required":false,"description":"A standard MIME type describing the format of the object data.","schema":{"type":"string"}},{"name":"Expires","in":"header","required":false,"description":"The date and time at which the object is no longer cacheable.","schema":{"type":"string","format":"date-time"}},{"name":"x-amz-server-side-encryption","in":"header","required":false,"description":"The server-side encryption algorithm used when storing this object in IONOS Object Storage (AES256).","schema":{"type":"string","enum":["AES256"]}},{"name":"x-amz-storage-class","in":"header","required":false,"description":"IONOS Object Storage uses the STANDARD Storage Class to store newly created objects. The STANDARD storage class provides high durability and high availability.","schema":{"type":"string","enum":["STANDARD"]}},{"name":"x-amz-website-redirect-location","in":"header","required":false,"description":"If the bucket is configured as a website, redirects requests for this object to another object in the same bucket or to an external URL. IONOS Object Storage stores the value of this header in the object metadata.","schema":{"type":"string"}},{"name":"x-amz-server-side-encryption-customer-algorithm","in":"header","required":false,"description":"Specifies the algorithm to use to when encrypting the object (AES256).","schema":{"type":"string"}},{"name":"x-amz-server-side-encryption-customer-key","in":"header","required":false,"description":"Specifies the customer-provided encryption key for IONOS Object Storage to use in encrypting data. This value is used to store the object and then it is discarded; IONOS Object Storage does not store the encryption key. The key must be appropriate for use with the algorithm specified in the `x-amz-server-side-encryption-customer-algorithm` header.","schema":{"type":"string","format":"password"}},{"name":"x-amz-server-side-encryption-customer-key-MD5","in":"header","required":false,"description":"Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. IONOS Object Storage uses this header for a message integrity check to ensure that the encryption key was transmitted without error.","schema":{"type":"string"}},{"name":"x-amz-object-lock-mode","in":"header","required":false,"description":"Specifies the Object Lock mode that you want to apply to the uploaded object.","schema":{"type":"string","enum":["GOVERNANCE","COMPLIANCE"]}},{"name":"x-amz-object-lock-retain-until-date","in":"header","required":false,"description":"Specifies the date and time when you want the Object Lock to expire.","schema":{"type":"string","format":"date-time"}},{"name":"x-amz-object-lock-legal-hold","in":"header","required":false,"description":"Specifies whether you want to apply a Legal Hold to the uploaded object.","schema":{"type":"string","enum":["ON","OFF"]}},{"name":"x-amz-meta-","in":"header","required":false,"description":"A map of metadata to store with the object.","schema":{"type":"string"}}]}}}} ``` ## ListParts > \

Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request. This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the \`max-parts\` request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an \`IsTruncated\` field with the value of true, and a \`NextPartNumberMarker\` element. In subsequent \`ListParts\` requests you can include the part-number-marker query string parameter and set its value to the \`NextPartNumberMarker\` field value from the previous response.\

```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"ListPartsOutput":{"type":"object","properties":{"Bucket":{"$ref":"#/components/schemas/BucketName"},"Key":{"$ref":"#/components/schemas/ObjectKey"},"UploadId":{"$ref":"#/components/schemas/MultipartUploadId"},"PartNumberMarker":{"description":"When a list is truncated, this element specifies the last part in the list, as well as the value to use for the part-number-marker request parameter in a subsequent request.","type":"integer"},"NextPartNumberMarker":{"description":"When a list is truncated, this element specifies the last part in the list, as well as the value to use for the part-number-marker request parameter in a subsequent request.","type":"string"},"MaxParts":{"description":"Maximum number of parts that were allowed in the response.","type":"string"},"IsTruncated":{"$ref":"#/components/schemas/IsTruncated"},"Parts":{"description":" Container for elements related to a particular part. A response can contain zero or more `Part` elements.","type":"array","items":{"$ref":"#/components/schemas/Part"}},"Initiator":{"$ref":"#/components/schemas/Initiator"},"Owner":{"$ref":"#/components/schemas/Owner"},"StorageClass":{"$ref":"#/components/schemas/StorageClass"}}},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}},"ObjectKey":{"description":"The object key.","type":"string","minLength":1,"maxLength":1024},"MultipartUploadId":{"description":"ID of the multipart upload.","type":"string"},"IsTruncated":{"type":"boolean","description":"A flag that indicates whether IONOS Object Storage returned all of the results that satisfied the search criteria. If your results were truncated, you can make a follow-up paginated request using the NextKeyMarker and NextVersionIdMarker response parameters as a starting place in another request to return the rest of the results.","enum":[true,false]},"Part":{"description":"Container for elements related to a part.","type":"object","properties":{"PartNumber":{"$ref":"#/components/schemas/PartNumber"},"LastModified":{"$ref":"#/components/schemas/LastModified"},"ETag":{"$ref":"#/components/schemas/ETag"},"Size":{"$ref":"#/components/schemas/Size"}},"xml":{"name":"Part"}},"PartNumber":{"description":"Part number that identifies the part.","type":"integer","minimum":1,"maximum":10000},"LastModified":{"description":"Creation date of the object.","type":"string","format":"date-time"},"ETag":{"description":"Entity tag that identifies the object's data.\nObjects with different object data will have different entity\ntags. The entity tag is an opaque string. The entity tag may or\nmay not be an MD5 digest of the object data. If the entity tag\nis not an MD5 digest of the object data, it will contain one or\nmore nonhexadecimal characters and/or will consist of less than\n32 or more than 32 hexadecimal digits.\n","type":"string"},"Size":{"description":"Size in bytes of the object","type":"integer","minimum":0,"maximum":5497558138880},"Initiator":{"description":"Container element that identifies who initiated the multipart upload.","type":"object","properties":{"ID":{"$ref":"#/components/schemas/ID"},"DisplayName":{"$ref":"#/components/schemas/DisplayName"}}},"ID":{"type":"integer","description":"Container for the Contract Number of the owner.","xml":{"name":"ID"}},"DisplayName":{"type":"string","description":"Container for the display name of the owner.","xml":{"name":"DisplayName"}},"Owner":{"type":"object","description":"Container for the owner's ID and display name.","properties":{"ID":{"$ref":"#/components/schemas/ID"},"DisplayName":{"$ref":"#/components/schemas/DisplayName"}},"xml":{"name":"Owner"}},"StorageClass":{"description":"Currently, only one storage class is available – `STANDARD`. \n","type":"string","enum":["STANDARD"]}}},"paths":{"/{Bucket}/{Key}?uploadId":{"get":{"tags":["Uploads"],"summary":"ListParts","operationId":"ListParts","description":"

Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request. This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the `max-parts` request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an `IsTruncated` field with the value of true, and a `NextPartNumberMarker` element. In subsequent `ListParts` requests you can include the part-number-marker query string parameter and set its value to the `NextPartNumberMarker` field value from the previous response.

","responses":{"200":{"description":"Success","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/ListPartsOutput"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"Key","in":"path","required":true,"description":"Object key for which the multipart upload was initiated.","schema":{"type":"string","minLength":1}},{"name":"max-parts","in":"query","required":false,"description":"Sets the maximum number of parts to return.","schema":{"type":"integer"}},{"name":"part-number-marker","in":"query","required":false,"description":"Specifies the part after which listing should begin. Only parts with higher part numbers will be listed.","schema":{"type":"integer"}},{"name":"uploadId","in":"query","required":true,"description":"Upload ID identifying the multipart upload whose parts are being listed.","schema":{"type":"string"}},{"name":"PartNumberMarker","in":"query","schema":{"type":"string"},"description":"Pagination token","required":false}]}}}} ``` ## CompleteMultipartUpload > \

Completes a multipart upload by assembling previously uploaded parts.\

\

After successfully uploading all relevant parts of an upload, you call this operation to complete the upload. When IONOS Object Storage receives this request, it concatenates all the parts in ascending order by part number to create a new object. The parts list must be included in the Complete Multipart Upload request. You must ensure that the parts list is complete. This operation concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the \`ETag\` value, returned after that part was uploaded.\

\

A Complete Multipart Upload request could take several minutes to process. After IONOS Object Storage begins processing the request, it sends an HTTP response header indicating a 200 OK response. While processing is in progress, IONOS Object Storage sends white space characters on a regular basis to keep the connection from timing out. Because a request may fail after receiving the initial 200 OK response, it is advisable to check the response body to establish whether the request was successful.\

\

\`CompleteMultipartUpload\` has the following special errors:\

\ ```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"CompleteMultipartUploadOutput":{"type":"object","properties":{"Location":{"description":"The URI that identifies the newly created object.","type":"string"},"Bucket":{"$ref":"#/components/schemas/BucketName"},"Key":{"$ref":"#/components/schemas/ObjectKey"},"ETag":{"$ref":"#/components/schemas/ETag"}}},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}},"ObjectKey":{"description":"The object key.","type":"string","minLength":1,"maxLength":1024},"ETag":{"description":"Entity tag that identifies the object's data.\nObjects with different object data will have different entity\ntags. The entity tag is an opaque string. The entity tag may or\nmay not be an MD5 digest of the object data. If the entity tag\nis not an MD5 digest of the object data, it will contain one or\nmore nonhexadecimal characters and/or will consist of less than\n32 or more than 32 hexadecimal digits.\n","type":"string"},"CompletedPartList":{"description":"Array of CompletedPart data types.","type":"array","items":{"$ref":"#/components/schemas/CompletedPart"},"xml":{"wrapped":false}},"CompletedPart":{"type":"object","properties":{"ETag":{"$ref":"#/components/schemas/ETag"},"PartNumber":{"$ref":"#/components/schemas/PartNumber"}},"description":"Details of the parts that were uploaded."},"PartNumber":{"description":"Part number that identifies the part.","type":"integer","minimum":1,"maximum":10000}}},"paths":{"/{Bucket}/{Key}?uploadId":{"post":{"tags":["Uploads"],"summary":"CompleteMultipartUpload","operationId":"CompleteMultipartUpload","description":"

Completes a multipart upload by assembling previously uploaded parts.

After successfully uploading all relevant parts of an upload, you call this operation to complete the upload. When IONOS Object Storage receives this request, it concatenates all the parts in ascending order by part number to create a new object. The parts list must be included in the Complete Multipart Upload request. You must ensure that the parts list is complete. This operation concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the `ETag` value, returned after that part was uploaded.

A Complete Multipart Upload request could take several minutes to process. After IONOS Object Storage begins processing the request, it sends an HTTP response header indicating a 200 OK response. While processing is in progress, IONOS Object Storage sends white space characters on a regular basis to keep the connection from timing out. Because a request may fail after receiving the initial 200 OK response, it is advisable to check the response body to establish whether the request was successful.

`CompleteMultipartUpload` has the following special errors:

","responses":{"200":{"description":"Success","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/CompleteMultipartUploadOutput"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"Key","in":"path","required":true,"description":"Object key for which the multipart upload was initiated.","schema":{"type":"string","minLength":1}},{"name":"uploadId","in":"query","required":true,"description":"ID for the initiated multipart upload.","schema":{"type":"string"}}],"requestBody":{"required":true,"content":{"application/xml":{"schema":{"title":"example","type":"object","properties":{"CompleteMultipartUpload":{"description":"The container for the completed multipart upload details.","type":"object","properties":{"Parts":{"$ref":"#/components/schemas/CompletedPartList"}}}}}}}}}}}} ``` ## UploadPart > \

Uploads a part in a multipart upload.\

\ \

In this operation, you provide part data in your request. However, you have an option to specify your existing IONOS Object Storage object as a data source for the part you are uploading. To upload a part from an existing object, you use the \`UploadPartCopy\` operation. \

\ \

You must initiate a multipart upload (see \`CreateMultipartUpload\`) before you can upload any part. In response to your initiate request, IONOS Object Storage returns an upload ID, a unique identifier, that you must include in your upload part request.\

\

Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.\

\

To ensure that data is not corrupted when traversing the network, specify the \`Content-MD5\` header in the upload part request. IONOS Object Storage checks the part data against the provided MD5 value. If they do not match, IONOS Object Storage returns an error. \

\

If the upload request is signed with Signature Version 4, then IONOS Object Storage uses the \`x-amz-content-sha256\` header as a checksum instead of \`Content-MD5\`. \

\

\Note:\ After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, IONOS Object Storage frees up the parts storage and stops charging you for the parts storage.\

```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"UploadPartOutput":{"type":"object","properties":{}},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}},"Content-MD5":{"type":"string","description":"The base64 encoded MD5 digest of the message (without the headers) according to\n[RFC 1864](http://www.ietf.org/rfc/rfc1864.txt).\n"}}},"paths":{"/{Bucket}/{Key}?uploadId":{"put":{"tags":["Uploads"],"summary":"UploadPart","operationId":"UploadPart","description":"

Uploads a part in a multipart upload.

In this operation, you provide part data in your request. However, you have an option to specify your existing IONOS Object Storage object as a data source for the part you are uploading. To upload a part from an existing object, you use the `UploadPartCopy` operation.

You must initiate a multipart upload (see `CreateMultipartUpload`) before you can upload any part. In response to your initiate request, IONOS Object Storage returns an upload ID, a unique identifier, that you must include in your upload part request.

Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.

To ensure that data is not corrupted when traversing the network, specify the `Content-MD5` header in the upload part request. IONOS Object Storage checks the part data against the provided MD5 value. If they do not match, IONOS Object Storage returns an error.

If the upload request is signed with Signature Version 4, then IONOS Object Storage uses the `x-amz-content-sha256` header as a checksum instead of `Content-MD5`.

Note: After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, IONOS Object Storage frees up the parts storage and stops charging you for the parts storage.

","responses":{"200":{"description":"Success","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/UploadPartOutput"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"Key","in":"path","required":true,"description":"Object key for which the multipart upload was initiated.","schema":{"type":"string","minLength":1}},{"name":"partNumber","in":"query","required":true,"description":"Part number of part being uploaded. This is a positive integer between 1 and 10,000.","schema":{"type":"integer"}},{"name":"uploadId","in":"query","required":true,"description":"Upload ID identifying the multipart upload whose part is being uploaded.","schema":{"type":"string"}},{"name":"Content-Length","in":"header","required":false,"description":"Size of the body in bytes. This parameter is useful when the size of the body cannot be determined automatically.","schema":{"type":"integer"}},{"name":"Content-MD5","in":"header","required":false,"schema":{"$ref":"#/components/schemas/Content-MD5"}},{"name":"x-amz-server-side-encryption-customer-algorithm","in":"header","required":false,"description":"Specifies the algorithm to use to when encrypting the object (AES256).","schema":{"type":"string","enum":["AES256"]}},{"name":"x-amz-server-side-encryption-customer-key","in":"header","required":false,"description":"Specifies the customer-provided encryption key for IONOS Object Storage to use in encrypting data. This value is used to store the object and then it is discarded; IONOS Object Storage does not store the encryption key. The key must be appropriate for use with the algorithm specified in the `x-amz-server-side-encryption-customer-algorithm header`. This must be the same encryption key specified in the initiate multipart upload request.","schema":{"type":"string","format":"password"}},{"name":"x-amz-server-side-encryption-customer-key-MD5","in":"header","required":false,"description":"Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. IONOS Object Storage uses this header for a message integrity check to ensure that the encryption key was transmitted without error.","schema":{"type":"string"}}],"requestBody":{"required":true,"content":{"application/xml":{"schema":{"type":"object","properties":{"Body":{"description":"Object data.","type":"string"}}}}}}}}}} ``` ## AbortMultipartUpload > \

This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts. \

```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"AbortMultipartUploadOutput":{"type":"object","properties":{}},"Error":{"type":"object","description":"Container for all error elements.","properties":{"Code":{"type":"string","enum":["AccessDenied","AccountProblem","AmbiguousGrantByEmailAddress","BadDigest","BucketAlreadyExists","BucketAlreadyOwnedByYou","BucketNotEmpty","CrossLocationLoggingProhibited","EntityTooSmall","EntityTooLarge","IllegalVersioningConfigurationException","IncorrectNumberOfFilesInPostRequest","InternalError","InvalidAccessKeyId","InvalidArgument","InvalidBucketName","InvalidBucketState","InvalidDigest","InvalidEncryptionAlgorithmError","InvalidLocationConstraint","InvalidObjectState","InvalidPart","InvalidPartOrder","InvalidPolicyDocument","InvalidRange","InvalidRequest","InvalidSecurity","InvalidTargetBucketForLogging","InvalidURI","KeyTooLong","MalformedACLError","MalformedPOSTRequest","MalformedXML","MaxMessageLengthExceeded","MaxPostPreDataLengthExceededError","MetadataTooLarge","MethodNotAllowed","MissingContentLength","MissingSecurityHeader","NoSuchBucket","NoSuchBucketPolicy","NoSuchKey","NoSuchLifecycleConfiguration","NoSuchReplicationConfiguration","NoSuchUpload","NoSuchVersion","NotImplemented","PermanentRedirect","PreconditionFailed","Redirect","RestoreAlreadyInProgress","RequestIsNotMultiPartContent","RequestTimeout","RequestTimeTooSkewed","SignatureDoesNotMatch","ServiceUnavailable","SlowDown","TemporaryRedirect","TooManyBuckets","UnexpectedContent","UnresolvableGrantByEmailAddress","UserKeyMustBeSpecified"],"description":"The error code is a string that uniquely identifies an error\ncondition. It is meant to be read and understood by programs\nthat detect and handle errors by type.\n\n## IONOS Object Storage error codes\n- AccessDenied\n - Description: Access Denied\n - HTTPStatus Code: 403 Forbidden\n- AccountProblem\n - Description: There is a problem with your IONOS Object Storage account that prevents the operation from completing successfully. Contact IONOS for further assistance.\n - HTTP Status Code: 403 Forbidden\n- AmbiguousGrantByEmailAddress\n - Description: The email address you provided is associated with more than one account.\n - HTTP Status Code: 400 Bad Request\n- BadDigest\n - Description: The Content-MD5 you specified did not match what we received.\n - HTTP Status Code: 400 Bad Request\n- BucketAlreadyExists\n - Description: The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.\n - HTTP Status Code: 409 Conflict\n- BucketAlreadyOwnedByYou\n - Description: The bucket you tried to create already exists, and you own it.\n - HTTP Code: 409 Conflict\n- BucketNotEmpty\n - Description: The bucket you tried to delete is not empty.\n - HTTP Status Code: 409 Conflict\n- CrossLocationLoggingProhibited\n - Description: Cross-location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location.\n - HTTP Status Code: 403 Forbidden\n- EntityTooSmall\n - Description: Your proposed upload is smaller than the minimum allowed object size.\n - HTTP Status Code: 400 Bad Request\n- EntityTooLarge\n - Description: Your proposed upload exceeds the maximum allowed object size.\n - HTTP Status Code: 400 Bad Request\n- IllegalVersioningConfigurationException\n - Description: Indicates that the versioning configuration specified in the request is invalid.\n - HTTP Status Code: 400 Bad Request\n- IncorrectNumberOfFilesInPostRequest\n - Description: POST requires exactly one file upload per request.\n - HTTP Status Code: 400 Bad Request\n- InternalError\n - Description: We encountered an internal error. Please try again.\n - HTTP Status Code: 500 Internal Server Error \n- InvalidAccessKeyId\n - Description: The IONOS Object Storage access key ID you provided does not exist in our records.\n - HTTP Status Code: 403 Forbidden\n- InvalidArgument\n - Description: Invalid Argument\n - HTTP Status Code: 400 Bad Request\n- InvalidBucketName\n - Description: The specified bucket is not valid.\n - HTTP Status Code: 400 Bad Request\n- InvalidBucketState\n - Description: The request is not valid with the current state of the bucket.\n - HTTP Status Code: 409 Conflict\n- InvalidDigest\n - Description: The Content-MD5 you specified is not valid.\n - HTTP Status Code: 400 Bad Request\n- InvalidEncryptionAlgorithmError\n - Description: The encryption request you specified is not valid. The valid value is AES256.\n - HTTP Status Code: 400 Bad Request\n- InvalidLocationConstraint\n - HTTP Status Code: 400 Bad Request\n- InvalidObjectState\n - Description: The operation is not valid for the current state of the object.\n - HTTP Status Code: 403 Forbidden\n- InvalidPart\n - Description: One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.\n - HTTP Status Code: 400 Bad Request\n- InvalidPartOrder\n - Description: The list of parts was not in ascending order. Parts list must be specified in order by part number.\n - HTTP Status Code: 400 Bad Request\n- InvalidPolicyDocument\n - Description: The content of the form does not meet the conditions specified in the policy document.\n - HTTP Status Code: 400 Bad Request\n- InvalidRange\n - Description: The requested range cannot be satisfied.\n - HTTP Status Code: 416 Requested Range Not Satisfiable\n- InvalidRequest\n - Description: Please use `AWS4-HMAC-SHA256`.\n - HTTP Status Code: 400 Bad Request\n- InvalidSecurity\n - Description: The provided security credentials are not valid.\n - HTTP Status Code: 403 Forbidden\n- InvalidTargetBucketForLogging\n - Description: The target bucket for logging does not exist, is not owned by you, or does not have the appropriate grants for the log-delivery group.\n - Status Code: 400 Bad Request\n- InvalidURI\n - Description: Couldn't parse the specified URI.\n - HTTP Status Code: 400 Bad Request\n- KeyTooLong\n - Description: Your key is too long.\n - HTTP Status Code: 400 Bad Request\n- MalformedACLError\n - Description: The XML you provided was not well-formed or did not validate against our published schema.\n - HTTP Status Code: 400 Bad Request\n- MalformedPOSTRequest\n - Description: The body of your POST request is not well-formed multipart/form-data.\n - HTTP Status Code: 400 Bad Request\n- MalformedXML\n - Description: This happens when the user sends malformed XML (XML that doesn't conform to the published XSD) for the configuration. The error message is, \"The XML you provided was not well-formed or did not validate against our published schema.\"\n - HTTP Status Code: 400 Bad Request\n- MaxMessageLengthExceeded\n - Description: Your request was too big.\n - HTTP Status Code: 400 Bad Request\n- MaxPostPreDataLengthExceededError\n - Description: Your POST request fields preceding the upload file were too large.\n - HTTP Status Code: 400 Bad Request\n- MetadataTooLarge\n - Description: Your metadata headers exceed the maximum allowed metadata size.\n - HTTP Status Code: 400 Bad Request\n- MethodNotAllowed\n - Description: The specified method is not allowed against this resource.\n - HTTP Status Code: 405 Method Not Allowed\n- MissingContentLength\n - Description: You must provide the Content-Length HTTP header.\n - HTTP Status Code: 411 Length Required\n- MissingSecurityHeader\n - Description: Your request is missing a required header.\n - HTTP Status Code: 400 Bad Request\n- NoSuchBucket\n - Description: The specified bucket does not exist.\n - HTTP Status Code: 404 Not Found\n- NoSuchBucketPolicy\n - Description: The specified bucket does not have a bucket policy.\n - HTTP Status Code: 404 Not Found\n- NoSuchKey\n - Description: The specified key does not exist.\n - HTTP Status Code:404 Not Found\n- NoSuchLifecycleConfiguration\n - Description: The lifecycle configuration does not exist.\n - HTTP Status Code: 404 Not Found\n- NoSuchReplicationConfiguration\n - Description: The replication configuration does not exist.\n - HTTP Status Code: 404 Not Found\n- NoSuchUpload\n - Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.\n - HTTP Status Code: 404 Not Found\n- NoSuchVersion\n - Description: Indicates that the version ID specified in the request does not match an existing version.\n - HTTP Status Code: 404 Not Found\n- NotImplemented\n - Description: A header you provided implies functionality that is not implemented.\n - HTTP Status Code: 501 Not Implemented\n- PermanentRedirect\n - Description: The bucket you are attempting to access must be addressed using the specified endpoint. Send all future requests to this endpoint.\n - HTTP Status Code: 301 Moved Permanently\n- PreconditionFailed\n - Description: At least one of the preconditions you specified did not hold.\n - HTTP Status Code: 412 Precondition Failed\n- Redirect\n - Description: Temporary redirect.\n - HTTP Status Code: 307 Moved Temporarily\n- RestoreAlreadyInProgress\n - Description: Object restore is already in progress.\n - HTTP Status Code: 409 Conflict\n- RequestIsNotMultiPartContent\n - Description: Bucket POST must be of the enclosure-type multipart/form-data.\n - HTTP Status Code: 400 Bad Request\n- RequestTimeout\n - Description: Your socket connection to the server was not read from or written to within the timeout period.\n - HTTP Status Code: 400 Bad Request\n- RequestTimeTooSkewed\n - Description: The difference between the request time and the server's time is too large.\n - HTTP Status Code: 403 Forbidden\n- SignatureDoesNotMatch\n - HTTP Status Code: 403 Forbidden\n- ServiceUnavailable\n - Description: Reduce your request rate.\n - HTTP Status Code: 503 Service Unavailable\n- SlowDown\n - Description: Reduce your request rate.\n - HTTP Status Code: 503 Slow Down\n- TemporaryRedirect\n - Description: You are being redirected to the bucket while DNS updates.\n - HTTP Status Code: 307 Moved Temporarily\n- TooManyBuckets\n - Description: You have attempted to create more buckets than allowed.\n - HTTP Status Code: 400 Bad Request\n- UnexpectedContent\n - Description: This request does not support content.\n - HTTP Status Code: 400 Bad Request\n- UnresolvableGrantByEmailAddress\n - Description: The email address you provided does not match any account on record.\n - HTTP Status Code: 400 Bad Request\n- UserKeyMustBeSpecified\n - Description: The bucket POST must contain the specified field name. If it is specified, check the order of the fields.\n - HTTP Status Code: 400 Bad Request\n"},"Message":{"type":"string","description":"Gives a brief English description of the issue."},"RequestId":{"type":"string"},"HostId":{"type":"string"}},"xml":{"name":"Error"}},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}}}},"paths":{"/{Bucket}/{Key}?uploadId":{"delete":{"tags":["Uploads"],"summary":"AbortMultipartUpload","operationId":"AbortMultipartUpload","description":"

This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts.

","responses":{"204":{"description":"Success","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/AbortMultipartUploadOutput"}}}},"480":{"description":"NoSuchUpload","headers":{},"content":{"aplication/xml":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"Key","in":"path","required":true,"description":"Key of the object for which the multipart upload was initiated.

**Possible values:** length ≥ 1

","schema":{"type":"string","minLength":1}},{"name":"uploadId","in":"query","required":true,"description":"Upload ID that identifies the multipart upload.","schema":{"type":"string"}}]}}}} ``` ## ListMultipartUploads > \

This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.\

\

This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the \`max-uploads\` parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an \`IsTruncated\` element with the value true. To list the additional multipart uploads, use the \`key-marker\` and \`upload-id-marker\` request parameters.\

\

In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.\

```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"ListMultipartUploadsOutput":{"type":"object","properties":{"Bucket":{"$ref":"#/components/schemas/BucketName"},"KeyMarker":{"description":"The key at or after which the listing began.","type":"string"},"UploadIdMarker":{"description":"Upload ID after which listing began.","type":"string"},"NextKeyMarker":{"description":"When a list is truncated, this element specifies the value that should be used for the key-marker request parameter in a subsequent request.","type":"string"},"Prefix":{"description":"When a prefix is provided in the request, this field contains the specified prefix. The result contains only keys starting with the specified prefix.","type":"string","minLength":1,"maxLength":1024},"Delimiter":{"description":"Contains the delimiter you specified in the request. If you don't specify a delimiter in your request, this element is absent from the response.","type":"string"},"NextUploadIdMarker":{"description":"When a list is truncated, this element specifies the value that should be used for the `upload-id-marker` request parameter in a subsequent request.","type":"string"},"MaxUploads":{"description":"Maximum number of multipart uploads that could have been included in the response.","type":"integer"},"IsTruncated":{"$ref":"#/components/schemas/IsTruncated"},"Uploads":{"description":"Container for elements related to a particular multipart upload. A response can contain zero or more `Upload` elements.","type":"array","items":{"$ref":"#/components/schemas/MultipartUpload"}},"CommonPrefixes":{"allOf":[{"$ref":"#/components/schemas/CommonPrefixList"},{"description":"If you specify a delimiter in the request, then the result returns each distinct key prefix containing the delimiter in a `CommonPrefixes` element. The distinct key prefixes are returned in the `Prefix` child element."}]},"EncodingType":{"$ref":"#/components/schemas/EncodingType"}}},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}},"IsTruncated":{"type":"boolean","description":"A flag that indicates whether IONOS Object Storage returned all of the results that satisfied the search criteria. If your results were truncated, you can make a follow-up paginated request using the NextKeyMarker and NextVersionIdMarker response parameters as a starting place in another request to return the rest of the results.","enum":[true,false]},"MultipartUpload":{"description":"Container for the `MultipartUpload` for the IONOS Object Storage object.","type":"object","properties":{"UploadId":{"$ref":"#/components/schemas/MultipartUploadId"},"Key":{"$ref":"#/components/schemas/ObjectKey"},"Initiated":{"description":"Date and time at which the multipart upload was initiated.","type":"string","format":"date-time"},"StorageClass":{"$ref":"#/components/schemas/StorageClass"},"Owner":{"$ref":"#/components/schemas/Owner"},"Initiator":{"$ref":"#/components/schemas/Initiator"}}},"MultipartUploadId":{"description":"ID of the multipart upload.","type":"string"},"ObjectKey":{"description":"The object key.","type":"string","minLength":1,"maxLength":1024},"StorageClass":{"description":"Currently, only one storage class is available – `STANDARD`. \n","type":"string","enum":["STANDARD"]},"Owner":{"type":"object","description":"Container for the owner's ID and display name.","properties":{"ID":{"$ref":"#/components/schemas/ID"},"DisplayName":{"$ref":"#/components/schemas/DisplayName"}},"xml":{"name":"Owner"}},"ID":{"type":"integer","description":"Container for the Contract Number of the owner.","xml":{"name":"ID"}},"DisplayName":{"type":"string","description":"Container for the display name of the owner.","xml":{"name":"DisplayName"}},"Initiator":{"description":"Container element that identifies who initiated the multipart upload.","type":"object","properties":{"ID":{"$ref":"#/components/schemas/ID"},"DisplayName":{"$ref":"#/components/schemas/DisplayName"}}},"CommonPrefixList":{"description":"All of the keys rolled up into a common prefix count as a single return when calculating the number of returns.","type":"array","items":{"$ref":"#/components/schemas/CommonPrefix"},"xml":{"wrapped":false}},"CommonPrefix":{"description":"Container for all (if there are any) keys between Prefix and the next occurrence of the string specified by a delimiter. CommonPrefixes lists keys that act like subdirectories in the directory specified by Prefix. For example, if the prefix is `notes/` and the delimiter is a slash (`/``) as in `notes/summer/july``, the common prefix is `notes/summer/``.","type":"object","properties":{"Prefix":{"$ref":"#/components/schemas/Prefix"}}},"Prefix":{"description":"Object key prefix that identifies one or more objects to which this rule applies. Replacement must be made for object keys containing special characters (such as carriage returns) when using XML requests.","type":"string","minLength":1,"maxLength":1024},"EncodingType":{"type":"string","enum":["url"],"description":"Encoding type used by IONOS Object Storage to encode object key names\nin the XML response. If you specify encoding-type request\nparameter, IONOS Object Storage includes this element in the response, and\nreturns encoded key name values in the following response\nelements: `KeyMarker`, `NextKeyMarker`, `Prefix`,\n`Key`, and `Delimiter`.\n"}}},"paths":{"/{Bucket}?uploads":{"get":{"tags":["Uploads"],"summary":"ListMultipartUploads","operationId":"ListMultipartUploads","description":"

This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.

This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the `max-uploads` parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an `IsTruncated` element with the value true. To list the additional multipart uploads, use the `key-marker` and `upload-id-marker` request parameters.

In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.

","responses":{"200":{"description":"Successful operation","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/ListMultipartUploadsOutput"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"delimiter","in":"query","required":false,"description":"

Character you use to group keys.

All keys that contain the same string between the prefix, if specified, and the first occurrence of the delimiter after the prefix are grouped under a single result element, `CommonPrefixes`. If you don't specify the prefix parameter, then the substring starts at the beginning of the key. The keys that are grouped under `CommonPrefixes` result element are not returned elsewhere in the response.

","schema":{"type":"string"}},{"name":"encoding-type","in":"query","required":false,"description":"","schema":{"type":"string","enum":["url"],"description":"Requests IONOS Object Storage to encode the object keys in the response and specifies the encoding method to use. An object key may contain any Unicode character; however, XML 1.0 parser cannot parse some characters, such as characters with an ASCII value from 0 to 10. For characters that are not supported in XML 1.0, you can add this parameter to request that IONOS Object Storage encode the keys in the response."}},{"name":"key-marker","in":"query","required":false,"description":"

Together with upload-id-marker, this parameter specifies the multipart upload after which listing should begin.

If `upload-id-marker` is not specified, only the keys lexicographically greater than the specified `key-marker` will be included in the list.

If `upload-id-marker` is specified, any multipart uploads for a key equal to the `key-marker` might also be included, provided those multipart uploads have upload IDs lexicographically greater than the specified `upload-id-marker`.

","schema":{"type":"string"}},{"name":"max-uploads","in":"query","required":false,"description":"Sets the maximum number of multipart uploads, from 1 to 1,000, to return in the response body. 1,000 is the maximum number of uploads that can be returned in a response.","schema":{"type":"integer"}},{"name":"prefix","in":"query","required":false,"description":"Lists in-progress uploads only for those keys that begin with the specified prefix. You can use prefixes to separate a bucket into different grouping of keys. (You can think of using prefix to make groups in the same way you'd use a folder in a file system.)","schema":{"type":"string"}},{"name":"upload-id-marker","in":"query","required":false,"description":"Together with key-marker, specifies the multipart upload after which listing should begin. If key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads for a key equal to the key-marker might be included in the list only if they have an upload ID lexicographically greater than the specified `upload-id-marker`.","schema":{"type":"string"}},{"name":"MaxUploads","in":"query","schema":{"type":"string"},"description":"Pagination limit","required":false},{"name":"KeyMarker","in":"query","schema":{"type":"string"},"description":"Pagination token","required":false},{"name":"UploadIdMarker","in":"query","schema":{"type":"string"},"description":"Pagination token","required":false},{"name":"uploads","in":"query","required":true,"schema":{"type":"boolean","enum":[true]},"allowEmptyValue":true}]}}}} ``` ## UploadPartCopy > \

Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header \`x-amz-copy-source\` in your request and a byte range by adding the request header \`x-amz-copy-source-range\` in your request. \

\

The minimum allowable part size for a multipart upload is 5 MB.\

\ \

Instead of using an existing object as part data, you might use the \`UploadPart\` operation and provide data in your request.\

\ \

You must initiate a multipart upload before you can upload any part. In response to your initiate request. IONOS Object Storage returns a unique identifier, the upload ID, that you must include in your upload part request.\

```json {"openapi":"3.0.3","info":{"title":"IONOS Object Storage API for contract-owned buckets","version":"2.0.3"},"tags":[{"name":"Uploads","description":"Multipart Uploads into a Bucket"}],"servers":[{"url":"https://s3.eu-central-3.ionoscloud.com","description":"The endpoint for the `eu-central-3` region (Berlin, Germany)"},{"url":"https://s3.us-central-1.ionoscloud.com","description":"The endpoint for the `us-central-1` region (Lenexa, USA)"}],"security":[{"hmac":[]}],"components":{"securitySchemes":{"hmac":{"type":"apiKey","name":"Authorization","in":"header","description":"IONOS Object Storage API requests are authenticated using the AWS signature. \nThe IONOS Object Storage API authenticates users using a customized HTTP scheme based on a [keyed-HMAC](https://en.wikipedia.org/wiki/HMAC) (Hash Message Authentication Code).\nThe process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.\n\n\n\nIn the **Authorization** tab for a request, select **AWS Signature** from the **Type** dropdown list.\nSpecify where Postman should append your authorization data using the **Add authorization data to** drop-down menu.\n\n* If you select **Request Headers**, Postman populates the **Headers** tab with Authorization and `X-Amz-` prefixed fields.\n\n* If you select **Request URL**, Postman populates the **Params** tab with authentication details prefixed with `X-Amz-`.\n\n\n**Note:** The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.\n\n* For **Access Key**, enter your `access key` directly in the fields or through variables for added security.\n\n* For **Secret Key**, enter your `secret key` directly in the fields or through variables for added security.\n\nAdvanced fields are optional, but Postman will attempt to generate them automatically if necessary.\n* For **AWS Region**, enter one of the [regions](#section/Endpoints) (`eu-central-3`) where your bucket is hosted.\n\n* For **Service Name**, enter `s3`. The name of the service that receives the requests.\n\n* For **Session Token**, **leave the field blank**. This is only required when temporary security credentials are used.\n"}},"schemas":{"UploadPartCopyOutput":{"type":"object","properties":{"CopyPartResult":{"$ref":"#/components/schemas/CopyPartResult"}}},"CopyPartResult":{"description":"Container for all response elements.","type":"object","properties":{"ETag":{"$ref":"#/components/schemas/ETag"},"LastModified":{"$ref":"#/components/schemas/LastModified"}}},"ETag":{"description":"Entity tag that identifies the object's data.\nObjects with different object data will have different entity\ntags. The entity tag is an opaque string. The entity tag may or\nmay not be an MD5 digest of the object data. If the entity tag\nis not an MD5 digest of the object data, it will contain one or\nmore nonhexadecimal characters and/or will consist of less than\n32 or more than 32 hexadecimal digits.\n","type":"string"},"LastModified":{"description":"Creation date of the object.","type":"string","format":"date-time"},"BucketName":{"description":"The bucket name.","type":"string","minLength":3,"maxLength":63,"xml":{"name":"Name"}}}},"paths":{"/{Bucket}/{Key}?x-amz-copy-source&partNumber&uploadId":{"put":{"tags":["Uploads"],"summary":"UploadPartCopy","operationId":"UploadPartCopy","description":"

Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header `x-amz-copy-source` in your request and a byte range by adding the request header `x-amz-copy-source-range` in your request.

The minimum allowable part size for a multipart upload is 5 MB.

Instead of using an existing object as part data, you might use the `UploadPart` operation and provide data in your request.

You must initiate a multipart upload before you can upload any part. In response to your initiate request. IONOS Object Storage returns a unique identifier, the upload ID, that you must include in your upload part request.

","responses":{"200":{"description":"Success","headers":{},"content":{"application/xml":{"schema":{"$ref":"#/components/schemas/UploadPartCopyOutput"}}}}},"parameters":[{"name":"Bucket","in":"path","required":true,"schema":{"$ref":"#/components/schemas/BucketName"}},{"name":"x-amz-copy-source","in":"header","required":true,"description":"

Specifies the source object for the copy operation.

","schema":{"type":"string","pattern":"\\/.+\\/.+"}},{"name":"x-amz-copy-source-if-match","in":"header","required":false,"description":"Copies the object if its entity tag (ETag) matches the specified tag.","schema":{"type":"string"}},{"name":"x-amz-copy-source-if-modified-since","in":"header","required":false,"description":"Copies the object if it has been modified since the specified time.","schema":{"type":"string","format":"date-time"}},{"name":"x-amz-copy-source-if-none-match","in":"header","required":false,"description":"Copies the object if its entity tag (ETag) is different than the specified ETag.","schema":{"type":"string"}},{"name":"x-amz-copy-source-if-unmodified-since","in":"header","required":false,"description":"Copies the object if it hasn't been modified since the specified time.","schema":{"type":"string","format":"date-time"}},{"name":"x-amz-copy-source-range","in":"header","required":false,"description":"The range of bytes to copy from the source object. The range value must use the form bytes=first-last, where the first and last are the zero-based byte offsets to copy. For example, bytes=0-9 indicates that you want to copy the first 10 bytes of the source. You can copy a range only if the source object is greater than 5 MB.","schema":{"type":"string"}},{"name":"Key","in":"path","required":true,"description":"Object key for which the multipart upload was initiated.","schema":{"type":"string","minLength":1}},{"name":"partNumber","in":"query","required":true,"description":"Part number of part being copied. This is a positive integer between 1 and 10,000.","schema":{"type":"integer"}},{"name":"uploadId","in":"query","required":true,"description":"Upload ID identifying the multipart upload whose part is being copied.","schema":{"type":"string"}},{"name":"x-amz-server-side-encryption-customer-algorithm","in":"header","required":false,"description":"Specifies the algorithm to use to when encrypting the object (AES256).","schema":{"type":"string","enum":["AES256"]}}]}}}} ```