Status Codes
When you call any of the Content Management REST resources, the Response header returns one of the standard HTTP status codes defined in the following table.
HTTP Status Code | Description |
---|---|
200 OK |
The request was successfully completed. A 200 status is returned for a successful GET or POST method. |
201 Created |
The request has been fulfilled and resulted in a new resource being created. The response includes a Location header containing the canonical URI for the newly created resource. A |
204 No Content |
The request is fulfilled, but there is no content available in the system. |
304 Not Modified |
The response is not modified at the server. |
400 Bad Request |
The request could not be processed because it contains missing or invalid information (such as a validation error on an input field or a missing required value). |
401 Unauthorized |
The request is not authorized. The authentication credentials included with this request are missing or invalid. |
403 Forbidden |
The user cannot be authenticated. The user does not have authorization to perform this request. |
404 Not Found |
The request includes a resource URI that does not exist. |
409 Conflict |
The request could not be completed due to a conflict with the current state of the resource. Either the version number does not match, or a duplicate resource was requested. |
500 Internal Server Error |
The server encountered an unexpected condition that prevented it from fulfilling the request. |
503 Service Unavailable |
The server is unable to handle the request due to temporary overloading or maintenance of the server. The REST web application is not currently running. |