--- layout: default ---

Accept-Encoding

IANA permanent request RFC 9110 2 spellings

Declared by 29 providers across 425 published specification files in the APIs.io network.

What this header is for, and how to use it →

A count here is providers whose published contract declares this header — not providers who send it. Response headers set at the edge rarely appear in an OpenAPI at all, so a low number can measure documentation practice rather than deployment.

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 (29)

adsbexchange aemo amadeus amazon-neptune amberdata autodesk-fusion bis brightcove conjur dow-jones ebay etsi eurostat expedia-group influxdata influxdb ion-group ocient salesforce snowflake socotra spp styra thingsboard us-bancorp viglink whitespace-london wise zuora

Explore

All headers Content Negotiation Guidance on headers.apievangelist.com