Ensure Consistent HTTP Status Codes for Non-Existent Resources etc

[Matte22]

API needs to ensure that API endpoints follow consistent and appropriate HTTP status codes for various scenarios, especially when dealing with resources that do not exist. Specifically, we want to avoid situations where an endpoint returns a 200 OK status for a user or other resource that doesn’t exist. Instead, such cases should return a 404 Not Found status code.

That is only one example scenario, but I am sure there could be others.

[Matte22]

see: updateUser