--- layout: default ---

Connection

IANA permanent response RFC 9110 2 spellings

Declared by 21 providers across 812 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.

Connectionconnection

The registry

Status	permanent
Reference	RFC 9110, Section 7.6.1: HTTP Semantics

Providers declaring it (21)

3gpp 73-strings amazon-api-gateway bitpowr-technologies-inc chaitin cohere conekta daytona-io deliverect gs1 kimi-moonshot linkedin render salesforce shyft upwind upwind-security userpilot vtex xflow zoominfo

Explore

All headers Connection & Transport Guidance on headers.apievangelist.com