Status Codes

When you call any of the Oracle Enterprise Manager 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.
202 Accepted	The request has been accepted for processing, but the processing has not been completed. The request may or may not eventually be acted upon, as it may be disallowed at the time processing actually takes place. When specifying an asynchronous (__detached=true) resource creation (for example, when deploying an application), or update (for example, when redeploying an application), a 202 is returned if the operation is still in progress. If __detached=false, a 202 may be returned if the underlying operation does not complete in a reasonable amount of time. The response contains a Location header of a job resource that the client should poll to determine when the job has finished. Also, returns an entity that contains the current state of the job
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). For limit parameters, the value cannot exceed the maximum of 2000.
400 Limit Exceeded	Fulling the request exceeds some Oracle-defined limit for the resource.
400 Related Resource Not Authorized Or Not Found	A referenced resource specified via the body is not found or the caller is not authorized to reference it.
401 Not Authenticated	The request is not authorized. The authentication credentials included with this request are missing or invalid.
403 Not Authorized	The user cannot be authenticated. The user has access to the resource, but does not have privileges required to perform the operation
404 Not Authorized Or Not Found	A resource specified in the request URI is not found or the caller is not authorized to see the resource.
405 Method Not Allowed	The HTTP verb specified in the request (DELETE, GET, POST, PUT) is not supported for this request URI.
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 Not Authorized Or Resource Already Exists	A resource is already present or the caller is not authorized to create the resource.
409 Incorrect State	An operation cannot be performed because the requested resource (or a resource the request depends on) is not "ready" for this request yet, but given some amount of time will be.
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).
429 Too Many Requests	Too many requests have been issued in too short of amount of time.
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 Oracle Enterprise Manager REST web application is not currently running.