News for hackers. Stuff that matters.

A comment on Best practices for REST API design (2020). Parent comment

Re:Best practices for REST API design (2020) by CharlesW on Monday February 22, 2021 @02:27PM (#26229263)
We could use a name for "standard JSON-over-HTTP stuff that's implemented in a variety of frameworks and libraries".

So what shall we call REST without HATEOAS[1]? "RESTless"?

[1] https://en.wikipedia.org/wiki/HATEOAS

[ Parent | on HN ]
Re:Best practices for REST API design (2020) by incrudible on Monday February 22, 2021 @03:08PM (#26229855)
No, a truly RESTless API must do away with all the other pointless HTTPisms in REST. If you're using any other method than GET or POST, or any other codes than 400 and 200, you're not truly RESTless.
[ Parent | on HN ]
Re:Best practices for REST API design (2020) by NanoWar on Monday February 22, 2021 @03:57PM (#26230509)
Most of the times I end up with put endpoints with verbs, because that often how businesses work. Objects and processes. Behind a REST resource there is a database table most in of the cases. But what if I want to send an email? POST /emails ? That's RESTless as well!
[ Parent | on HN ]