<h2>Why GET and POST weren’t enough, and how the newly standardized QUERY method (RFC 10008) will change REST API design.</h2>
If you work with REST APIs, you know the classics: <code>GET</code>, <code>POST</code>, <code>PUT</code>, <code>PATCH</code>, and <code>DELETE</code>. But did you know that as of June 2026, the IETF standardised a brand-new HTTP method?
Meet <code>QUERY</code> (RFC 10008).
It is the first major standard HTTP verb added since <code>PATCH</code> in 2010, and it solves a frustrating architectural problem developers have been applying “hacky” workarounds to for over a decade and a half.
Here is a look at why we needed it, how it works, concrete examples of where it shines, and the reality of framework support today.
Read the full article here
<a href="https://smali-kazmi.medium.com/the-new-http-query-method-solving-a-16-year-api-dilemma-9ae1c13a248d" target="_blank" rel="noopener nofollow">https://smali-kazmi.medium.com/the-new-http-query-method-solving-a-16-year-api-dilemma-9ae1c13a248d</a>

Mudaser Ali

The IETF has standardized a new HTTP method called QUERY (RFC 10008) as of June 2026, the first major new HTTP verb since PATCH was added in 2010. It addresses a long-standing architectural problem in REST API design where complex search or filter queries needed a request body but GET semantics were semantically correct — forcing developers into workarounds like using POST for read-only queries. The post covers why GET and POST were insufficient, how QUERY works, use cases where it excels, and the current state of framework support.

The New HTTP QUERY Method: Solving a 16-Year API Dilemma