S3 · Objects

DeleteObjects

POST/{bucket}?delete

Deletes up to 1,000 objects in one request.

Each key gets its own result. A key that fails does not stop the others. An Object with a VersionId removes that version for good. Without a VersionId, storage removes the object. In a bucket with versioning on, it adds a delete marker and keeps the versions.

View as Markdown

Role: Editor or higher
Support: Supported
Auth: SigV4 with your API key

Up to 1,000 keys. Each key gets its own result. A VersionId removes that version. Quiet mode works.
A key with no object comes back as an Error with the code NoSuchKey.
Storage does not need Content-MD5.

Request

https://wspq7ws2np5l8z4.storage.beta.graphon.sh/support-tickets?delete

POST /support-tickets?delete HTTP/1.1
Host: wspq7ws2np5l8z4.storage.beta.graphon.sh
x-amz-date: 20261007T093000Z
x-amz-content-sha256: c7c851ceb4359b2eff263321acec9a3b9804f1cd80750006d5d348989187998e
Authorization: AWS4-HMAC-SHA256 Credential=<ACCESS_KEY_ID>/20261007/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=<SIGNATURE>
Content-Length: 156

<Delete xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
  <Object>
    <Key>a.json</Key>
  </Object>
  <Object>
    <Key>b.json</Key>
  </Object>
</Delete>

Replace wspq7ws2np5l8z4 with your workspace ID. HTTP shows the signed request on the wire. The aws CLI and the SDKs sign for you. The CLI uses the graphon profile, and the SDK samples read GRAPHON_API_KEY.

Response

200

The result for each key. Check the Error elements, because the status is 200 even when keys fail.

HTTP/1.1 200 OK
Content-Type: application/xml
x-amz-request-id: 4F8A2C7D1E6B4093A5C2D8E1F7B3A960

<?xml version="1.0" encoding="UTF-8"?>
<DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
  <Deleted>
    <Key>a.json</Key>
  </Deleted>
  <Error>
    <Key>b.json</Key>
    <Code>NoSuchKey</Code>
    <Message>The specified key does not exist.</Message>
  </Error>
</DeleteResult>

Path parameters

bucketstringrequired

The bucket name.

Query parameters

deleteflagrequired

Selects this operation. Send it with no value.

Headers

x-amz-expected-bucket-ownerstringoptional

The workspace ID that must own the bucket. Another owner returns 403 AccessDenied.

Request body

Deleteobjectrequired

The root element.

Quietbooleanoptional

Send true to return only the errors.

Default: false

Objectarrayrequired

One element for each key, up to 1,000.

Responses

200OK

The result for each key. Check the Error elements, because the status is 200 even when keys fail.

application/xml

DeleteResultobjectrequired

The root element.

Deletedarray

One element for each deleted key. Quiet mode leaves it out.

Errorarray

One element for each key that failed.

Errors

Select an error in the response example to see its XML body. Any request can also get the common errors, such as SignatureDoesNotMatch.

404NoSuchBucket

No bucket has this name, or the bucket was deleted.

What to do: Check the bucket name. ListBuckets shows the buckets of the workspace.

403AccessDenied

The key does not have the role for this operation, or the bucket is in another workspace.

What to do: Use a key of the workspace that owns the bucket, with the role above.

Was this page helpful?