Choosing an HTTP Status Code
    > I’m not completely sure they do matter.
    > There’s a lot of smart people at Facebook and they
    > built an API that only ever returns 200.

This is the best bit of the article.Most (many?) APIs, whether or not their authors call them REST, are single URL APIs that you throw JSON/YAML/whatever at. If the caller is going to get back a serialized status message (["Not found"]), then the HTTP request was successful, and it should return 200.I'm not sure why people insist on spreading their APIs out between the transport and content layer.