Error handling in our REST API is fully based on HTTP error code= s. As a web developer, you are familiar with the most common ones: 401= Unauthorized, 404 Not Found or 500 Internal Server Error. The REST AP= I uses those, along with a few more, to provide error handling.
As explained in the specifications, a few error codes apply to most reso= urces (if they are applicable)
The server encountered an unexpected condition, usually an excepti= on, which prevented it from fulfilling the request: database down, permissi= ons or configuration error.
Returned when the requested method has not yet been implemented. A= s of eZ Publish 5.0, most of user, group, content, location and content typ= e have been implemented. Some of their methods, as well as other features, = may return a 501.
Returned when the request failed because the request object was no= t found. You should be familiar with this one.
Returned when the requested REST API resource doesn't support the = HTTP verb that was used.
Returned when an accept header sent with the requested isn't suppo= rted.
It is up to you, in your implementation, to handle those codes by = checking if an error code (4xx or 5xx) was returned instead of an expected = 2xx or 3xx.