s3.bucket-objects.delete-versionsDelete up to 1000 versions for good; deleting a delete marker undeletes
POST /s3/api/buckets/{name}/objects/delete-versionsIAM s3:DeleteObjectVersionChanges stateDestructive
Answers { deleted, errors }, each with key and versionId.
Request syntax
POST /s3/api/buckets/{name}/objects/delete-versions
{
"versions": "array of json"
}Path parameters
nameRequiredstring
Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/
Request body
versionsRequiredarray of json
The versions to delete for good, as { key, versionId }; the versionId of a delete marker undeletes the key
Response
200; data is { deleted: [{ key, versionId }], errors: [{ key, versionId, message }] }: what was deleted and what was refused.
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:DeleteObjectVersion 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 delete-versions name --versions '["example"]'curl -X POST "https://console.platform-development.deutschecloud.app/s3/api/buckets/name/objects/delete-versions" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"versions":["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_delete-versions.