Set-Cookie
Declared by 51 providers across 9877 published specification files in the APIs.io network.
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.
Set-Cookieset-cookie
Reached by regulation
The registry
| Status | permanent |
|---|---|
| Reference | RFC-ietf-httpbis-rfc6265bis-22, Section 5.8.1: Cookies: HTTP State Management Mechanism |
Providers declaring it (51)
0xarchive acoustic adobe-suite aleph-alpha amcs-group authelia autodesk-fusion backstage beacon-roofing-supply beehero bonitasoft cisco-nexus citrix-netscaler cloudquery cybereason devtron dream-sports euler hanko ibm-mq interchecks intersight juniper lakefs lenovo linkedin mcafee mist mist-ai netcracker opaque open-food-facts oracle-e-business-suite passbolt pred qliksense salesforce saml sap-business-one sciencelogic shopify shyft spacetrack sso tower trellix-web-gateway tttech volumez websphere windmill zoominfo
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.