Content-Disposition
Declared by 131 providers across 7131 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-Dispositioncontent-disposition
The registry
| Status | permanent |
|---|---|
| Reference | RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) |
Providers declaring it (131)
3shake 8x8 accredify0604 acoustic acronis adp aeris aiera amazon-s3 api-snap appdirect argyle atlassian autocontent-api autodesk-fusion banqu binarly bitbucket bitbucket-pipelines bloomreach box bridge california-privacy-protection-agency canonical canopy ccpa chili-piper cint clickhouse cloudflare cloudflare-r2 convertapi conxai cybelangel densify didit digital-ocean docker-hub dotdigital dow-jones dsv dust-tt earnipay ebay elk-stack engineering-platform enrich-so factset gemini-trust getaccept gladly goharbor greynoise harness here heyform hopper-com hugging-face-transformers infobip interchecks intersight kubeshop kuehne-nagel lalal-ai landmark-information lawvu limitless-ai listmonk logikio loop lorum mediamath meow messagebird method-financial methodfi microcks microsoft-azure mirakl moodys-rms morningstar ncino nedap netbird netcracker nhost observepoint oracle oracle-cloud oracle-platforms palo-alto-networks plex ppro primitive progress-software pruna-ai qliksense qualio rentberry root runloop-ai sageox schematic sciencelogic silverflow slashid specterops spectro-cloud stellar strivacity thriva top-group tradeshift tttech uniuni upguard va vcv vectorizer-ai versapay voltair webex wikimedia wikipedia writer wso2 xflow yoobic zamzar zoho zoho-crm
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.