Content-Encoding
Declared by 51 providers across 2485 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.
Content-Encodingcontent-encoding
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 8.4: HTTP Semantics |
Providers declaring it (51)
adobe-suite aiera amazon-s3 axiom-co azure-log-analytics bird bitpowr-technologies-inc cerebras-systems cloudflare-r2 cms datadog dow-jones dtn engineering-platform etsi factset galileo-technologies gameanalytics here honeycomb-io influxdata influxdb kudosity lemlist mastodon microsoft-azure microsoft-azure-monitor moodys-rms moogsoft new-relic newscred nuon oanda optimizely oracle oracle-cloud palo-alto-networks salesforce sendgrid shyft silverflow stardog styra vayana-network vectorizer-ai vtex wikimedia wikipedia wise zoominfo zuora
Explore
All headers Representation Metadata 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.