Working draft published for the 'GraphQL over HTTP' specification (Jul 24, 2025)

GraphQLAPIDevOps

Key update

A working draft of the GraphQL over HTTP specification was published (working draft dated Jul 24, 2025), formally defining how to encode GraphQL requests and responses over HTTP — including a new response media type (application/graphql-response+json), canonical request parameter names, recommended URL patterns (e.g., /graphql), and clear guidance on HTTP status-code semantics for GraphQL responses. (graphql.github.io)

Why it matters

This draft moves the ecosystem from de-facto conventions to an explicit, interoperable contract. Practically, the spec lets servers and clients agree on when a non-2xx status code is meaningful (the spec introduces a dedicated media type so intermediaries and tooling can trust HTTP status codes), prescribes request/response shapes and content negotiation, and recommends URL and caching behavior — all of which directly affect server implementations, client libraries, proxies, CDNs and observability tooling. (graphql.github.io)

For developers that run or integrate GraphQL services: you should plan to (a) add support for the new media type alongside application/json, (b) audit intermediaries (reverse proxies, CDNs, API gateways) to ensure they don’t rewrite or drop GraphQL responses, and (c) update client libraries and server frameworks to follow the spec’s request parameter and URL guidance to improve caching, error semantics, and tooling interoperability. The spec is still a draft, but its recommendations are already precise enough to drive concrete compatibility and deployment changes. (github.com)

Source

Read Next