Cross Domain · specification · IETF — HTTP Working Group (httpbis), Standards Track. Authors Julian Reschke (greenbytes), James M. Snell (Cloudflare) and Mike Bishop (Akamai); responsible AD Gorry Fairhurst, document shepherd Mark Nottingham.

The HTTP QUERY Method (RFC 10008)

RFC 10008 defines QUERY, an HTTP method that is safe and idempotent like GET but carries a request body like POST. It exists for the operation every API eventually needs and no existing method fits — a read whose parameters are too large or too structured for a URL. Because it is safe, a QUERY response is cacheable and a QUERY request may be automatically retried, neither of which is true of the POST /…/search workaround it replaces. It also registers the Accept-Query response header, through which a resource advertises that it accepts QUERY and which query media types it understands.

IETF — HTTP Working Group (httpbis), Standards Track. Authors Julian Reschke (greenbytes), James M. Snell (Cloudflare) and Mike Bishop (Akamai); responsible AD Gorry Fairhurst, document shepherd Mark Nottingham.Governing body
2026First published
RFC 10008 (June 2026), Proposed StandardCurrent version
No — a protocol method, not a documen...Machine-readable schema
1providers in the catalog

Also known as QUERY, QUERY Method, RFC 10008, Safe Method with Body, draft-ietf-httpbis-safe-method-w-body.

Providers that carry HTTP QUERY Method 1

These providers' own APIs.json profiles carry HTTP QUERY Method as a tag — the provider's statement that the standard is part of what it does. APIs.io has not verified the implementation on this page; the de facto profiles on this site are where that measurement exists. Ordered by Kin Score.

Read from the API Evangelist standards directory, facts verified 2026-08-27. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.