Error Responses
When ever the request fails, a HTTP error status and an ERS response content is returned back to client in order to describe the problem. The following table describes possible errors:
| Error Code | Description | HTTP STATUS |
|---|---|---|
| VERSION_EXCEPTION | Occurs when the resource version sent in the request content is not supported anymore by the server. | 415 |
| MEDIA_TYPE_EXCEPTION | Occurs when the media type sent by the client in the ACCEPT or Content-Type headers is invalid. | 415 |
| UNSUPPORTED_RESOURCE_EXCEPTION | Occurs when the resource as appear in the URI, does not supported by the server. | 400 |
| UNSUPPORTED_METHOD_EXCEPTION | Occurs when the request method type is not supported for the specified URI. | 400 |
| QUERY_VALIDATION_EXCEPTION | Occurs when the search filter or paging parameters are not valid. | 400 |
| SCHEMA_VALIDATION_EXCEPTION | Occurs when the resource validation against its schema fails. | 400 |
| APPLICATION_RESOURCE_VALIDATION_EXCEPTION | Occurs when the resource semantic validation does not meets the requirements | 400 |
| INTERNAL_EXCEPTION | Any unexpected internal server error that occurs at runtime. | 500 |
| CONVERSION_EXCEPTION | Occurs for some internal conversions and should be treated as INTERNAL_EXCEPTION | 500 |
| CRUD_OPERATION_EXCEPTION | Occurs during the CRUD operation execution and should be treated as INTERNAL_EXCEPTION | 500 |
The following example demonstrates a response with media type error that happens when the client sent an unsupported mediatype in the ACCEPT header:
The following example demonstrates a response with a schema validation error that happens because a mandatory field - 'name' is missing
