Aren't message bodies on GET supposed not to impact the returned result at all?
Re:HTTP/1.1 just got a major update
by colanderman on Saturday June 07, 2014 @09:54AM
(#7862089)
Is that really restful though? If you need that many parameters to specify which resource you mean, you lose pretty much all of the benefit of a restful architecture.
GET vs. POST is a question of whether the request is intended to change state. Using JSON for a query is nice for preserving structure (e.g. nesting a Boolean expressions, not needing PHP-style array notation, etc.) but it doesn't change the idea that it's a GET request which can safely be repeated without affecting server state, may be cached for other clients, etc.
That said, I POST my search params to Elasticsearch anyways.