How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HTTP Headers

A header is the most-used extension point in HTTP and the part of an API a contract most often fails to describe. This is the catalog: every field in the IANA registry, every header the API Evangelist network observes in a published contract, and the standards, regulations, guidance and governance rules that reach each one.

302
headers catalogued
5,074
distinct names observed
33
reached by regulation
67
used by 25+ providers

How this was measured

Every in: header parameter and every headers: mapping key was extracted from 119,030 published specification files across all 26,641 providers in the API Evangelist network, then folded case-insensitively per RFC 9110 §5.1. A header earns a page here if it is registered with IANA, reached by a regulation, or declared by at least 25 distinct providers. The other 4,933 names are real but are almost entirely one-off vendor fields; they are searchable on APIs.io rather than written up here.

Authorization & Scope (2)

Headers that carry what the caller is permitted to do, once identity is settled: scope, tenancy, delegated consent, acting-on-behalf-of.

Privacy & Consent (7)

Headers carrying a person's preference or a legal consent artifact. The smallest category in the catalog by adoption and the largest by regulatory consequence.

Idempotency & Reliability (7)

Headers that make a retry safe. Almost entirely a payments-industry invention that the rest of the API economy has not adopted.

Versioning & Lifecycle (9)

Headers that carry version, deprecation and end-of-life. The category the catalog shows to be almost entirely unused, which is a finding rather than a gap in the data.

Async & Long-Running (5)

Headers for work that does not finish inside the request: preference for async handling, polling locations, progress, retry timing.

Agent & Bot Identity (8)

Headers by which an automated caller identifies itself, and by which a server decides what to serve it. The newest category, and the one with the least settled vocabulary.