Depends on the API I guess. If you are using graphql or jsonrpc or something, then sure return a 200 "The request was ok, but go look in errors" If you are us

Depends on the API I guess. If you are using graphql or jsonrpc or something, then sure return a 200 "The request was ok, but go look in errors" If you are using REST then I think it is fine to return a 404 - "The thing you wanted doesnt exist". That seems correct to me, the thing you wanted to get doesn't exist. The fact that /non-existant-path also returns a 404 is also correct, the thing/resource you wanted doesn't exist.