How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Amazon S3 Tagging API

Operations for managing bucket and object tags

Amazon S3 Tagging API is one of 12 APIs that Amazon S3 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Tagging. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, pricing, a getting-started guide, authentication docs, and 2 JSON Schemas.

This API exposes 3 operations across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2006-03-01.

Requests are made against 2 base URLs: https://s3.{region}.amazonaws.com, https://{bucket}.s3.{region}.amazonaws.com.

3 operations 1 paths 3 schemas 1 DELETE1 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2006-03-01
Base URL
https://s3.amazonaws.com
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Amazon S3 Tagging API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (sigv4). By default, every request must be authenticated.

  • sigv4 — AWS Signature Version 4 authentication. All S3 REST API requests must be signed using AWS Signature Version 4. The signature includes the request date, region,…

Paths & Operations 3

Across 1 path, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Tagging 3

Operations for managing bucket and object tags

GET
/{Bucket}?tagging
Amazon S3 Get Bucket Tagging
GetBucketTagging 2 params → 200403404
PUT
/{Bucket}?tagging
Amazon S3 Put Bucket Tagging
PutBucketTagging 4 params body → 204403
DELETE
/{Bucket}?tagging
Amazon S3 Delete Bucket Tagging
DeleteBucketTagging 2 params → 204403

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Error (5 properties), Tag (2 properties), Tagging (1 property). Each schema is shown below with its type and property counts.

Tagging
object
Container for TagSet elements.
1 property 1 required
Error
object
Container for all error elements.
5 properties
Tag
object
A container of a key value name pair.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amazon-s3-tagging-api-openapi.yml Raw ↑

Other APIs Amazon S3 publishes across the network.

Amazon S3 Access Control API
Amazon S3 Access Grants API
Amazon S3 Access Points API
Amazon S3 Batch Operations API
Amazon S3 Bucket Configuration API
Amazon S3 Buckets API
Amazon S3 Multi-Region Access Points API
Amazon S3 Multipart Upload API
Amazon S3 Objects API
Amazon S3 Public Access Block API
Amazon S3 Storage Lens API
Where this information came from

This is an independent, third-party profile of Amazon S3 Tagging API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.