The Referer HTTP header — agent & bot identity, RFC 9110, declared by 9 providers in the API Evangelist catalog.
Referer
Agent & Bot Identity IANA permanent request 2 spellings
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
Referer is agent & bot identity — 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.
The registry
Listed in the IANA HTTP Field Name Registry as a permanent entry. Defined in RFC 9110, Section 10.1.3: HTTP Semantics.
In the catalog
Declared by 9 providers across 39 published specification files in the API Evangelist catalog, where it appears as a request header — sent by the client.
It is spelled 2 different ways across those contracts — referer, Referer. HTTP field names are case-insensitive (RFC 9110, §5.1), so every one of these is the same header. They are not the same string, which is why generated clients disagree about it.
Governed by these rules
Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.
OpenAPI Components Headers Error error
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Components Headers Info info
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Headers Hyphenated Pascal Case error
HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.
Guidance: Naming →