Amazon S3 · Schema
UploadPartRequest
ArchivesAmazon Web ServicesBackupCloud StorageData StorageObject StorageScalable StorageStorage
Properties
| Name | Type | Description |
|---|---|---|
| Body | string | Object data. |
| Bucket | string | The name of the bucket to which the multipart upload was initiated. Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format Bu |
| ContentLength | integer | Size of the body in bytes. This parameter is useful when the size of the body cannot be determined automatically. |
| ContentMD5 | string | The Base64 encoded 128-bit MD5 digest of the part data. This parameter is auto-populated when using the command from the CLI. This parameter is required if object lock parameters are specified. This f |
| ChecksumAlgorithm | string | Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any additional functionality if you don't use the SDK. When you send this header, |
| ChecksumCRC32 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 32-bit CRC32 checksum of the obj |
| ChecksumCRC32C | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 32-bit CRC32C checksum of the ob |
| ChecksumCRC64NVME | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME checksum of the |
| ChecksumSHA1 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 160-bit SHA1 digest of the objec |
| ChecksumSHA256 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 256-bit SHA256 digest of the obj |
| ChecksumSHA512 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 512-bit SHA512 digest of the par |
| ChecksumMD5 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 128-bit MD5 digest of the part. |
| ChecksumXXHASH64 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit XXHASH64 checksum of the |
| ChecksumXXHASH3 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit XXHASH3 checksum of the p |
| ChecksumXXHASH128 | string | This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 128-bit XXHASH128 checksum of th |
| Key | string | Object key for which the multipart upload was initiated. |
| PartNumber | integer | Part number of part being uploaded. This is a positive integer between 1 and 10,000. |
| UploadId | string | Upload ID identifying the multipart upload whose part is being uploaded. |
| SSECustomerAlgorithm | string | Specifies the algorithm to use when encrypting the object (for example, AES256). This functionality is not supported for directory buckets. |
| SSECustomerKey | string | Specifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is used to store the object and then it is discarded; Amazon S3 does not store the encryption key. Th |
| SSECustomerKeyMD5 | string | Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error. |
| RequestPayer | string | |
| ExpectedBucketOwner | string | The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied) |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/amazon-s3/json-schema/amazon-s3-upload-part-request-schema.json",
"title": "UploadPartRequest",
"x-generated": "2026-11-11",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/amazon-s3-operations-api-openapi.yml#/components/schemas/UploadPartRequest",
"type": "object",
"properties": {
"Body": {
"type": "string",
"format": "byte",
"description": "Object data."
},
"Bucket": {
"type": "string",
"description": "The name of the bucket to which the multipart upload was initiated. Directory buckets - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must follow the format bucket-base-name--zone-id--x-s3 (for example, amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Ama"
},
"ContentLength": {
"type": "integer",
"description": "Size of the body in bytes. This parameter is useful when the size of the body cannot be determined automatically."
},
"ContentMD5": {
"type": "string",
"description": "The Base64 encoded 128-bit MD5 digest of the part data. This parameter is auto-populated when using the command from the CLI. This parameter is required if object lock parameters are specified. This functionality is not supported for directory buckets."
},
"ChecksumAlgorithm": {
"type": "string",
"enum": [
"CRC32",
"CRC32C",
"SHA1",
"SHA256",
"CRC64NVME",
"SHA512",
"MD5",
"XXHASH64",
"XXHASH3",
"XXHASH128"
],
"description": "Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any additional functionality if you don't use the SDK. When you send this header, there must be a corresponding x-amz-checksum or x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more information, see Checking object integrity in the Amazon S3 User Guide. If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm parameter. This checksum algorithm must be the same for all parts and it m"
},
"ChecksumCRC32": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 32-bit CRC32 checksum of the object. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumCRC32C": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 32-bit CRC32C checksum of the object. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumCRC64NVME": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit CRC64NVME checksum of the part. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumSHA1": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 160-bit SHA1 digest of the object. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumSHA256": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 256-bit SHA256 digest of the object. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumSHA512": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 512-bit SHA512 digest of the part. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumMD5": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 128-bit MD5 digest of the part. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumXXHASH64": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit XXHASH64 checksum of the part. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumXXHASH3": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 64-bit XXHASH3 checksum of the part. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"ChecksumXXHASH128": {
"type": "string",
"description": "This header can be used as a data integrity check to verify that the data received is the same data that was originally sent. This header specifies the Base64 encoded, 128-bit XXHASH128 checksum of the part. For more information, see Checking object integrity in the Amazon S3 User Guide."
},
"Key": {
"type": "string",
"description": "Object key for which the multipart upload was initiated."
},
"PartNumber": {
"type": "integer",
"description": "Part number of part being uploaded. This is a positive integer between 1 and 10,000."
},
"UploadId": {
"type": "string",
"description": "Upload ID identifying the multipart upload whose part is being uploaded."
},
"SSECustomerAlgorithm": {
"type": "string",
"description": "Specifies the algorithm to use when encrypting the object (for example, AES256). This functionality is not supported for directory buckets."
},
"SSECustomerKey": {
"type": "string",
"description": "Specifies the customer-provided encryption key for Amazon S3 to use in encrypting data. This value is used to store the object and then it is discarded; Amazon S3 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. This functionality is not supported for directory buckets."
},
"SSECustomerKeyMD5": {
"type": "string",
"description": "Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption key was transmitted without error. This functionality is not supported for directory buckets."
},
"RequestPayer": {
"type": "string",
"enum": [
"requester"
]
},
"ExpectedBucketOwner": {
"type": "string",
"description": "The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden (access denied)."
}
},
"required": [
"Bucket",
"Key",
"PartNumber",
"UploadId"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/amazon-s3-upload-part-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.