s3.bucket-objects.deleteDelete up to 1000 objects
Answers { deleted, errors }. A key that does not exist counts as deleted, as in S3.
Request syntax
POST /s3/api/buckets/{name}/objects/delete
{
"keys": "array of string"
}Path parameters
nameRequiredstring
Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/
Request body
keysRequiredarray of string
Keys of the objects to delete; in a versioned bucket each gets a delete marker and its versions stay
Constraints: min 1 chars
Response
200; data is { deleted: [key], errors: [{ key, message }] }: the keys deleted and those that were refused or failed.
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:DeleteObject 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 name --keys '["example"]'curl -X POST "https://console.platform-development.deutschecloud.app/s3/api/buckets/name/objects/delete" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"keys":["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.