--- layout: default ---

Cookie

IANA permanent request 2 spellings

Declared by 7 providers across 75 published specification files in the APIs.io network.

What this header is for, and how to use it →

A count here is providers whose published contract declares this header — not providers who send it. Response headers set at the edge rarely appear in an OpenAPI at all, so a low number can measure documentation practice rather than deployment.

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.

Cookiecookie

The registry

Statuspermanent
ReferenceRFC-ietf-httpbis-rfc6265bis-22, Section 5.8.1: Cookies: HTTP State Management Mechanism

Providers declaring it (7)

chaitin macrometa mattermost mtn-group ory plansource vtex

Explore

All headers Authentication Guidance on headers.apievangelist.com