Hacker News Reader

That’s pretty bad design. Only GETs should include a querystring. Links should only read, not create, update or delete.

> Only GETs should include a querystring.

Why?

Because HTTP is a lot more sophisticated than anyone cares to acknowledge. The entire premise of "REST", as it is academically defined, is an oversimplification of how any non-trivial API would actually work. The only good part is the notion of "state transfer".

Not a REST API, but I've found it particularly useful to include query parameters in a POST endpoint that implements a generic webhook ingester.

The query parameters allow us to specify our own metadata when configuring the webhook events in the remote application, without having to modify our own code to add new routes.

What does that have to do with query parameters in non-GET requests?

Reply on news.ycombinator.com