.jpg)
The HTTP protocol has been the backbone of web communication for decades, but its evolution does not stop. After sixteen years without new additions, the IETF has standardized the QUERY method (RFC 10008), designed to resolve one of the most common tensions in REST API design: how to perform complex read requests without forcing the semantics of GET or POST. This method combines the safety and idempotence of GET with the flexibility of a request body typical of POST, allowing advanced filters, nested objects, and search criteria to be sent in JSON format without saturating the URL or compromising cacheability. In environments where custom applications are developed, this standardization represents a significant advance towards cleaner and more predictable APIs.
The need for QUERY arises from everyday reality: when a search system requires multiple conditions, sorting, pagination, or aggregations, the URL becomes a tangled mess that is difficult to encode and maintain. Many teams opt for POST for these operations —even if they only retrieve data— because the request body allows complex structures. However, POST does not guarantee idempotence; in the event of a timeout or network error, retrying the same request could have unwanted effects if the server is not correctly implemented. QUERY, being safe and idempotent by definition, allows proxies, caches, and clients to treat the request as a read-only operation, improving the reliability of systems that handle large volumes of data, such as those managing AI for businesses or AWS and Azure cloud services platforms.
From a practical perspective, the adoption of QUERY will not be immediate: most frameworks —Spring Boot, Express, FastAPI— do not yet offer native support, and infrastructure tools like reverse proxies and API gateways need updates. However, understanding its design helps plan future architectures. At Q2BSTUDIO, as a software development company, we closely follow these evolutions because they directly impact the quality of the solutions we deliver. The standardization of methods like QUERY facilitates the creation of more robust custom software, especially when combined with artificial intelligence for semantic search processes or with business intelligence services where complex queries are an everyday occurrence.
While the industry adapts, the recommendation remains to use GET for simple requests and POST for complex searches, but we can already anticipate the change. Initiatives such as process automation or the implementation of AI agents will benefit from a protocol that understands the difference between reading and modifying without ambiguity. Ultimately, QUERY will not replace GET or POST, but it offers the balance that was missing to design more expressive and efficient APIs, one more step towards the maturity of the semantic web that more and more companies need.
