GuidesAPI Reference
API Reference

Uploads a part or creates a new part from part of an existing blob.

post
https://use.apilookup.for.a.base.url/layers//keysMultipart//parts

Upload or copy a single part of a multipart upload or multipart copy for the blob. Every part except the last one must have a minimum 5 MB of data and maximum of 96 MB. The length of every part except the last must be a multiple of 1MB (1024KB). The maximum number of parts is 10,000.

Path Params
string
required

The ID of the parent layer for this blob.

string
required

The identifier of the multipart upload (token). This token is returned when the multipart upload is initiated.

Query Params
int32
required

This parameter relates to upload and copy. The number of the part for the multipart upload or copy. The numbers of the upload parts must start from 1, be no greater than 10,000 and be consecutive. Parts uploaded with the same partNumber are overridden. Do not reuse the same partNumber when retrying an upload or copy in an error situation (network problems, 4xx or 5xx responses). Reusing the same partNumber in a retry may cause the publication to fail.

string

Copy part from an existing object, use range to specify which parts of the object to copy.

Body Params

The body relates to upload only. The data to upload as part of the blob.

Headers
int64

This header relates to upload only. Size of the entity-body, in bytes. For more information, see RFC 7230, section 3.3.2: Content-Length.

string

This header relates to upload only. A standard MIME type describing the format of the blob data. For more information, see RFC 2616, section 14.17: Content-Type. The value of this header must match the content type specified in the contentType field when the multipart upload was initialized, and this content type must also match the content type specified in the layer's configuration.

string

This header/parameter relates to object copy using the 'source' parameter. Use this parameter to copy a specific slice of the blob like this: Range: bytes=0-1048575. This parameter is compliant with RFC 7233, but note that this parameter only supports a single byte range and both begin and end values of the range must be specified. The range begin value must be multiple of 1MB (1024KB). The length of every part except the last must be a multiple of 1MB (1024KB). The range parameter can also be specified as a query parameter, for example range=bytes=0-1048575.

string

This header can be used as a data integrity check to verify that the data received by the server is the same data that was originally sent by the client. This header specifies the lowercase Hex encoded 32-bit CRC32C checksum of the object or 128-bit MD5 digest or 160-bit SHA1 digest or 256-bit SHA256 digest. You can choose one of the following Secure Hash Algorithms (SHA) or Cyclic Redundancy Check (CRC) checksum algorithms to calculate the digest value:

  • CRC-32C
  • MD5
  • SHA1
  • SHA256

Value of the header is a combination algorithm name and digest in following format: "Algorithm:Digest". If the digest values calculated on the client side doesn't match to the digest on the server side, server generates Bad Request error.

Responses

Updated last month

Language
Credentials
Bearer
JWT
Response 
Click Try It! to start a request and see the response here! Or choose an example:
application/json
*/*
Updated last month