RFC 10008 introduces a new HTTP method, QUERY, that lets clients submit a query body while keeping the request safe and idempotent. The Internet Engineering Task Force defined the spec in 2026 to fill a gap between GET and POST. QUERY accepts a request body, unlike GET, and signals that the server will not alter state.

The method is marked safe, meaning it cannot change the target resource, and idempotent, allowing retries on failure. A successful 2xx response may include a Content‑Location or Location header, giving the client a URI to re‑run the query without resubmitting the body. Servers can also redirect with 301 or 308 codes.

By formalizing QUERY, IETF gives developers a standard way to perform complex queries over HTTP without sacrificing caching or retry logic. Implementers can now expose query endpoints that return deterministic results, simplifying client logic and improving interoperability across services. The RFC is now an Internet Standard, ready for adoption in modern APIs.

Adopting QUERY can reduce round‑trip overhead in data‑heavy applications and enable better caching strategies. Because the method is idempotent, intermediaries can safely store responses, improving network efficiency. Organizations that already use JSON‑based query bodies will find the transition seamless, as the method aligns with existing serialization practices.