QUERY was just ratified as RFC 10008 (June 2026), the first new HTTP method since PATCH back in 2010. It’s safe, idempotent, and cacheable like GET, but carries a request body like POST, which makes it the natural fit for search / filter / GraphQL-style read endpoints. Tooling is already adopting it (Node.js, .NET 10, OpenAPI 3.2), so external services that experiences talk to will start exposing QUERY endpoints.
It would be great if RequestAsync supported it too. Right now Method = "QUERY" isn’t accepted, it’s aborted before the request is even sent, so there’s currently no way to reach those endpoints from an experience. Adding QUERY to the accepted methods (the same way PATCH, PUT, and DELETE were added over time) would let experiences use it as adoption grows.
Repro:
HttpService:RequestAsync({
Url = "http://httpbin.org/anything",
Method = "QUERY", -- HttpError: Aborted; identical request with "POST" returns 200
Headers = { ["Content-Type"] = "application/json" },
Body = HttpService:JSONEncode({ filter = { city = "Berlin" } }),
})