Status Codes

When you call any of the Oracle Identity Governance (OIG) 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 201 status is returned from a synchronous resource creation or an asynchronous resource creation that completed before the response was returned.
204 No Content	The server has fulfilled the request but does not return a response body.
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, a missing required value, and so on).
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.
406 Not Acceptable	The resource identified by this request is not capable of generating a representation corresponding to one of the media types in the Accept header of the request. For example, the client's Accept header request XML be returned, but the resource can only return JSON.
406 Not Acceptable	The resource identified by this request is not capable of generating a representation corresponding to one of the media types in the Accept header of the request. For example, the client's Accept header request XML be returned, but the resource can only return JSON.
409 Conflict	The request could not be processed because of a conflict in the request.
412 Precondition Failed	Failed to update as resource ID changed on the server last retrieved.
415 Not Acceptable	The client's ContentType header is not correct (for example, the client attempts to send the request in XML, but the resource can only accept JSON).
422 Unprocessable Entity	The server understands the content type of the request entity and the syntax of the request entity is correct, but is unable to process the contained instructions.
424 Failed Dependency	The request failed due to failure of a previous request.
500 Internal Server Error	The server encountered an unexpected condition that prevented it from fulfilling the request.
501 Not Impplemented	The server does not recognize the request method, or the request method is not supported.