How to (and how not to) design REST APIs

Re:How to (and how not to) design REST APIs by hnbad on Wednesday November 01, 2023 @06:25PM (#38106221)

> Fielding's own examples from his blog, how'd you turn a lamp on and off via REST? Would you be like `POST /lamp`? No. It's unclear WTF is happening.

No, of course you'd be like `PATCH {"light": "off"} /lamp`!

Kidding of course but it's true that REST purity does not make for intuitive APIs in complex real-world problem domains.

[ Parent | on HN ]

Re:How to (and how not to) design REST APIs by rswail on Thursday November 02, 2023 @01:57AM (#38109490)

In HTML, you could have a FORM with the URL of /lamp/switch that you PUT.

[ Parent | on HN ]

Re:How to (and how not to) design REST APIs by 3cats-in-a-coat on Thursday November 02, 2023 @08:10AM (#38112387)

So you're putting a switch. Great API design.

[ Parent | on HN ]

Re:How to (and how not to) design REST APIs by cxr on Thursday November 02, 2023 @07:27PM (#38121887)

PUT is not a valid method from an HTML form. Only GET or POST are permitted.

[ Parent | on HN ]

Re:How to (and how not to) design REST APIs by 3cats-in-a-coat on Thursday November 02, 2023 @09:54PM (#38123386)

This kind of reveals a little secret of many of the REST gurus. They have no clue what they're talking about.

[ Parent | on HN ]