Range
Declared by 49 providers across 218 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.
Rangerange
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 14.2: HTTP Semantics |
Providers declaring it (49)
adobe-suite amazon-healthomics amazon-s3 armor artifactory autodesk autodesk-fusion brewpage cloudflare-r2 cubefs dotcms engineering-platform entergram etsi filebase here heroku hugging-face-transformers infobip instabase kiteworks lakefs marketo microsoft-azure microsoft-azure-blob-storage nasuni nhost oracle oracle-cloud oracle-platforms oxide-computer peertube progress-software qliksense rhombus-systems rook sentinel-hub supabase the-climate-corporation tigris-data toornament uclouvain university-of-texas-at-austin upwind wazo wikimedia wikipedia xquik-api zot
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.