Security

x-amz-credential

`x-amz-credential` appears on schema objects and properties. Its value is a string. Used by 8 providers across 9 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz tooling rather than by OpenAPI. Observed values include `string`, `123456789/20191005/us-east-1/s3/aws4_request`, `/20240618/local/s3/aws4_request`, `ASIA6QZJ64OPIKV7FRVX/20220127/us-east-1/s3/aws4_request`. Consistent with security — this is inferred from where the key appears and what it carries, not from any published definition.

Security x-amz- namespace derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
22 occurrences
9 documents
8 providers
vendor-named

Where it appears

Location in the documentOccurrences
schema 19
response 3

What its value looks like

Value shapeOccurrences
string16
object6

Observed values

Sampled from the specifications, most frequent first.

string123456789/20191005/us-east-1/s3/aws4_request/20240618/local/s3/aws4_requestASIA6QZJ64OPIKV7FRVX/20220127/us-east-1/s3/aws4_requestCREDENTIAL_GOES_HERE

Providers publishing it

All 8.

confluentconfluent-the-data-streaming-platformdocspringnarminewscredpinterestpunchhvdocipher

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the security job.