Announcing the GraphQL over HTTP specification
Web page · https://graphql.org/blog/2026-11-12-announcing-the-graphql-over-http-spec
First seen by Oriel on .
AI summary
The first GraphQL over HTTP specification supplements transport-agnostic GraphQL with standardized HTTP behavior intended to improve interoperability and observability across servers, clients, proxies, and other services.
- A new response media type lets clients identify well-formed GraphQL responses regardless of HTTP status, avoiding the previous reliance on universal 200 responses.
- The specification provides status-code guidance, including 405 for mutations over GET, 406 and 415 for unsupported media types, 431 for oversized headers, and 500 for server errors.
- It introduces 294 Partial Success for responses containing both data and errors, with further explanation in non-normative notes.
- The document standardizes established practices covering URLs, GET and POST requests, JSON encoding, headers, security, partial success, and future compatibility.
- Planned work includes supporting the proposed QUERY HTTP verb and standardizing persisted documents and request batching, particularly for composite schemas and uncontrolled schemas.
#graphql #http #api standards #observability
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 8, latest observation ; +7 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 0, latest observation ; 0 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | klmtb1 | https://graphql.org/blog/2026-11-12-announcing-the-graphql-over-http-spec/ Read discussion |