[evnix]

This is the way to go, pretty much solves, 404 resource not found or route not found. But you will get laughed at by so called architectural dogmatists. Remember we aren't really doing REST, it's just RPC and let's call it that.

Shoehorning http protocols error codes as application error codes, drinking the cool aid and calling it best practice is beyond bizzare.

[marcus_holmes]

Agree. "200 - successfully failed to do the thing" is valid and useful.

500 is "failed to do anything at all"