S3 · Object tags

DeleteObjectTagging

DELETE/{bucket}/{key}?tagging

Removes every tag from an object.

The object keeps its bytes and metadata. Only the tags go.

View as Markdown

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

Empties the tag set.
Storage changes the current version. It ignores versionId.

Request

https://wspq7ws2np5l8z4.storage.beta.graphon.sh/support-tickets/a.json?tagging

DELETE /support-tickets/a.json?tagging HTTP/1.1
Host: wspq7ws2np5l8z4.storage.beta.graphon.sh
x-amz-date: 20261007T093000Z
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
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>

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

204

Storage removed the tags.

HTTP/1.1 204 No Content
x-amz-request-id: 4F8A2C7D1E6B4093A5C2D8E1F7B3A960

Path parameters

bucketstringrequired

The bucket name.

keystringrequired

The object key. Keep each / as it is. Percent-encode the other reserved characters.

Query parameters

taggingflagrequired

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.

Responses

204No Content

Storage removed the tags.

This response has no body.

Errors

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

404NoSuchKey

The bucket has no object at this key, or no version with this versionId.

What to do: Check the key and the versionId.

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?