E Status Codes

REST APIs support HTTP response status codes, where the specific code that is returned depends on the HTTP method invoked on the request.

REST APIs support the HTTP codes listed in the following table.

Table E-1 HTTP Codes Supported by REST APIs

HTTP Code	Description
200 OK	Request successfully executed and the response has content.
201 Created	Resource successfully created. The response contains the created resource.
204 No Content	Request successfully executed and the response doesn't have content.
304 Not Modified	According to the provided ETag, the resource was not modified.
400 Bad Request	The request could not be understood by the server due to malformed syntax.
401 Unauthorized	The server is refusing to service the request because the resource of the request is secured and authentication has not yet been provided.
404 Not Found	The requested resource was not found.
406 Not Acceptable	The business object identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
412 Precondition failed	The business object state in the server side doesn't match the provided ETag.
415 Unsupported Media Type	The server is refusing to service the request because the entity of the request is in a format not supported by the requested business object for the requested method.
500 Internal Server Error	The server encountered an unexpected condition which prevented it from fulfilling the request.