WWW-Authenticate
Declared by 43 providers across 1986 published specification files in the APIs.io network.
Spelled 3 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
WWW-Authenticatewww-authenticateWww-Authenticate
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 11.6.1: HTTP Semantics |
Providers declaring it (43)
adyen aedifion agendapro airbus-oneatlas antavo anyapi apiary artifactory bindbee bird bloomreach builtwith c-hoare-and-co cdr-energy cisco-umbrella confluent confluent-the-data-streaming-platform doit dream-sports etsi expedia-group griffin here holidu leadping lucent mastercard microsoft-azure moneris nift qualtrics salesforce salesgraph shyft sourcepoint superdial tsb-bank va-gov vectorizer-ai websitepros xquik-api zuora zyte
Explore
All headers Authentication Guidance on headers.apievangelist.com
Work with this as data
Every header here is available over the APIs.io API and to AI agents over MCP. HTTP Headers is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.