|
Siebel REST API Guide > Overview of Using the Siebel REST API >
About Standard HTTP Status Codes and Error Messages
Siebel CRM 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. Table 7 contains the standard HTTP status codes used by the Siebel REST API.
Table 7. Standard HTTP Status Codes and Error Messages
|
|
|
200 |
OK |
The request successfully executed and the response has content. |
204 |
No Content |
The request successfully executed, but the content is not available. For example, the content was deleted. |
401 |
Unauthorized |
The request did not have valid authorization credentials. |
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. |
|
