Accept-Encoding
Declared by 39 providers across 708 published specification files in the APIs.io network.
Spelled 2 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.
Accept-Encodingaccept-encoding
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 12.5.3: HTTP Semantics |
Providers declaring it (39)
adobe-suite adsbexchange aemo amadeus amazon-neptune amberdata autodesk-fusion bis brightcove cdisc cms conjur dow-jones dtn dxfeed ebay etsi eurostat expedia-group gracenote here influxdata influxdb ion-group ocient salesforce siftingio snowflake socotra sovrn spp styra thingsboard tiledb us-bancorp viglink whitespace-london wise zuora
Explore
All headers Content Negotiation 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.