The X-Amz-SignedHeaders HTTP header — authentication, declared by 96 providers in the API Evangelist catalog.
X-Amz-SignedHeaders
Authentication de facto — unregistered request
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
X-Amz-SignedHeaders is authentication — Headers that carry who the caller is — credentials, tokens, keys, signatures of identity. The most declared category in the catalog and the most inconsistently spelled.
The registry
Not registered with IANA. It is a de facto or vendor field — real, widely used, and governed by nothing but convention.
In the catalog
Declared by 96 providers across 3,439 published specification files in the API Evangelist catalog, where it appears as a request header — sent by the client.
Governed by these rules
Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.
OpenAPI Components Headers Error error
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Components Headers Info info
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Headers Hyphenated Pascal Case error
HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.
Guidance: Naming →OpenAPI Security Schemes API Keys In Header Error error
Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations have a in of header set.
Guidance: Security →OpenAPI Security Schemes API Keys Info info
Having components security schemes which possesses an api-key property that allows to configure how API keys are applied to operations.
Guidance: Security →