s3.bucket-objects.multipart-partsThe parts of an unfinished upload stored so far, to resume it
POST /s3/api/buckets/{name}/objects/multipart/partsIAM s3:PutObjectChanges stateDestructive
Answers { parts: [{ partNumber, etag, size }] }, every part (not paged).
Request syntax
POST /s3/api/buckets/{name}/objects/multipart/parts
{
"key": "string",
"uploadId": "string"
}Path parameters
nameRequiredstring
Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/
Request body
keyRequiredstring
Key the upload was started for
Constraints: min 1 chars
uploadIdRequiredstring
From multipart create
Constraints: 1-1024 chars
Response
200; data is { parts: [{ partNumber, etag, size }] }, every part stored so far.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow s3:PutObject on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud s3 bucket-objects multipart-parts name --key example --upload-id examplecurl -X POST "https://console.platform-development.deutschecloud.app/s3/api/buckets/name/objects/multipart/parts" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"key":"example","uploadId":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_s3_bucket-objects_multipart-parts.