Transfer-Encoding
IANA permanent
response
RFC 9112
2 spellings
Declared by 16 providers across 1297 published specification files in the APIs.io network.
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.
Transfer-Encodingtransfer-encoding
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9112, Section 6.1: HTTP Semantics |
Providers declaring it (16)
aleph-alpha bird bitpowr-technologies-inc factset groq influxdb linkedin microsoft-azure openai portkey salesforce shyft speechify sportradar unrealspeech zoominfo
Explore
All headers Connection & Transport Guidance on headers.apievangelist.com