RFC 10008, published recently, defines a new HTTP method named QUERY designed to improve how RESTful APIs handle data fetching. This method aims to address limitations in existing HTTP methods such as GET and POST, which have been the standard for decades. The QUERY method was introduced to provide a clearer semantic for querying operations, distinct from other HTTP actions, according to kreya.app.
The new QUERY method allows clients to explicitly indicate that their intention is to perform a query operation, rather than relying on the overloaded semantics of GET requests. While GET has traditionally been used for data retrieval, it comes with constraints such as limited support in HTML forms and restrictions imposed by proxies and firewalls. QUERY is intended to overcome these issues by being a dedicated method for queries, improving clarity and potentially enabling better handling by intermediaries, as explained in the kreya.app blog post dated June 17, 2026.
This development matters because HTTP methods have long been foundational to web communication, yet their semantics have evolved with workarounds and implicit behaviors. Introducing QUERY could standardize query operations, reducing ambiguity and improving API design. It follows a trend of refining HTTP to better suit modern web applications. While GET and POST remain widely supported, QUERY could offer a more precise tool for developers, similar to how other methods like PUT and DELETE serve specific purposes.
Kreya, an API client tool, released version 1.20.0 on June 17, 2026, which supports the new QUERY method along with other improvements such as operation-based login. This adoption by tools signals early ecosystem support for QUERY, which could influence broader acceptance and implementation in web servers and proxies.