I've developed both REST and XMLRPC API's. The right tool for the right job. Sometimes REST is that tool. I also tend to combine JSON with REST. I still enjoy

I've developed both REST and XMLRPC API's. The right tool for the right job. Sometimes REST is that tool. I also tend to combine JSON with REST. I still enjoy using proper HTTP codes when possible. So if you're sending a json payload to update an object that doesn't exist I'll give you 404. But at the same time you're able to create that object by defining its properties in a json payload in the next request and not some obscure url parameters or POST parameters. I don't see anything wrong with using proper HTTP methods and return codes when possible.