I think the standard approach to RESTful searching is this:
GET /users?parameter1=value1¶meter2=value2¶meter3=value3¶meter4=value4
But I want to do something like this:
GET /users
# Request body:
{
"parameter1": "value1",
"parameter2": "value2",
"parameter3": "value3",
"parameter4": "value4"
}
Update: I can't use GET in the above manner because some devices to not respect body content of GET requests. So I would have to use POST instead.
Is RESTful religiosity the only reason that I shouldn't use POST to send JSON data to an /api/search
endpoint, as opposed to using the URI?
Are there any technical and demonstrable dangers in using POST in this manner?
I'm aware that this is similar to the following:
How to design RESTful search/filtering?
But I'm asking something more specific: namely, what are some reasons that this would be a bad approach, other than "it doesn't fit convention".