Accept-Language
Declared by 90 providers across 3446 published specification files in the APIs.io network.
Spelled 3 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-Languageaccept-languageAccept-language
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 12.5.4: HTTP Semantics |
Providers declaring it (90)
acoustic adopets adp airbus-oneatlas algolia antavo apifreaks-api-hub-for-developers appdirect autodesk-bim360 autodesk-fusion back-market bamboo ccp-games cdk-global certifaction chaitin cisco-catalyst-center cisco-secure-firewall citi conekta credilinqai customer-io dow-jones dow-jones-developer-platform dtn ebay edamam-recipes elastic-path engineering-platform eurostat ev-energy eve-online factiva finalcad freepik genesys getty-images harvard harver ikea keyper lean-technologies london-stock-exchange-group mastercard mealie mention microsoft-azure moneris moodys-rms morningstar mx-platform mx-technologies newstore novopayment okta optimizely oracle-e-business-suite oracle-hospitality palenca-vech patch-io politecnico-di-torino punchh qliksense quandoo ripe-insurance rwth-aachen-university smart-pension smartnews tapcart tickitto top-group transit treadio tribe-payments university-of-helsinki uphold vendasta viator visa visier wallapop wazo who wikimedia wikipedia wikisource wiktionary wise zamna zhipu-ai
Explore
All headers Content Negotiation 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.