key
Declared by 52 providers across 442 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.
keyKeyKEY
Providers declaring it (52)
abuseipdb activecampaign arduino beeceptor boom-ai builtwith carsxe cilium cisco-ise cloudrf controlup elk-stack emailrep engineering-platform enphase frontline gameball gemini gleap greynoise holded ilert integration-os kibana knock-app komerce kong landmark-information leap lilt meteosource-air-quality-data-api mockaroo offendersearch offendersearch-api okta ordnance-survey ordway pagerduty pagesnap postman red-hat sigma-computing sk-telecom suprsend systran tenable therundown tickitto uniform upwind viam what3words
Explore
All headers Authentication 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.