POST request does not have to go to a queried resource. Instead it can go to /search/resource and create new instance of search. Whether a server decides to per

POST request does not have to go to a queried resource. Instead it can go to /search/resource and create new instance of search. Whether a server decides to persist it or not, will be an implementation detail. There’s also an option to use the following semantics (with a number of nice bonuses): POST /resource/views {some definition of response structure and allowed parameters} GET /resource?view=…&params=… The whole idea of GraphQL revolves around the possibility of client to query the whole graph of the persistent model. This idea itself is questionable for many reasons - coupling, security etc. In many cases where I have seen it, classic REST with HAL (client-server) or plain old SQL (server-server) would be more than enough.