Timeline for Why do so many standards for JSON API response formats contain a "success" property in the response body instead of just using HTTP status codes?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2022 at 0:23 | comment | added | imel96 | @CodeCaster yes, maybe. What I'm saying is HTTP status code is sufficient for REST. HTTP status code is not needed for RPC. It's up to the developer what to use if they mix REST and RPC together | |
| Apr 2, 2022 at 11:46 | comment | added | CodeCaster | @imel96 most APIs aren't pure REST, not everything is treatable as a resource. | |
| Mar 30, 2022 at 6:00 | comment | added | imel96 |
Your linked question has REST tag, so I'd say in many cases, returning "success": true is a sign doing RPC rather than REST. There are enough status codes to say about the object representation sent to the server. It doesn't make sense to say "success" when receiving an object. E.g. if client sent an "inflated football", the server can say "Ok" (REST). If a client say "inflate the football" then the server can respond with "success" (RPC).
|
|
| Mar 25, 2022 at 23:29 | comment | added | njzk2 | that one is easy: footballs don't have laces | |
| Mar 25, 2022 at 13:00 | history | answered | CodeCaster | CC BY-SA 4.0 |