Standard HTTP Status Codes

Oracle CRM On Demand REST API uses standard HTTP status codes to indicate the success or failure of API calls. When an error occurs or when a response is successful, the response header contains an HTTP code, and the response body usually contains a message accompanying the HTTP response code with additional information about the error. For additional information about Oracle CRM On Demand API error formats, see Error Response Format.

The following table contains the standard HTTP status codes used by the Oracle CRM On Demand REST API.

Table Standard HTTP Status Codes and Errors Messages

HTTP Code	Error Message	Description
200	OK	The request successfully executed, and the response has content.
201	Created	The resource was successfully created and the response contains the created resource.
204	No Content	The request successfully executed, but content is not available. For example, the content was deleted.
302	Found	The requested resource resides temporarily under a different URL. The response includes redirection to the correct URL.
304	Not Modified	The resource was not modified.
400	Bad Request	The server could not interpret the request.
401	Unauthorized	The request did not have valid authorization credentials.
403	Forbidden	The request has been refused because of insufficient privileges. Verify that the signed-in user has the appropriate privileges.
404	Not Found	The requested resource was not found because of an invalid object name.
405	Not Allowed	The request is not allowed.
406	Not Acceptable	The resource identified by the request is capable of generating only response entities that have content characteristics that are not acceptable according to the accept headers sent in the request.
415	Unsupported Media Type	The data format of the request body, specified in the Content-Type header, is not supported by the targeted resource.
500	Internal Server Error	The server encountered an unexpected error, preventing it from fulfilling the request.