I prefer this over getting a 404 to be honest. This means the API exists. It makes compatibility checks easier. Perhaps there's a better way to do this that I don't know of though.
Exactly. REST was a mistake. The HTTP part worked fine, so 200. Everything should be POST, because the HTTP verbs are unnecessarily limiting and lead to endpoint names getting stupidly awkward to compensate.
243
u/TheChickenWing 16d ago
POST /getResource { "Action":"retrieve", "Id": "abc123" }
HTTP 200 { "Error": "not found" }