Status Codes

When you call any of the Compute Classic REST resources, the Response header returns one of the standard HTTP status codes defined in the following table.

Note:

Success codes are documented in the topics that describe the individual methods.

HTTP Response Code	Error Description
4xx	APIClientError A client side error, in line with 4xx errors in HTTP.
400	Bad Request The request contains invalid parameters.
401	APIUnauthorizedError The request requires user authentication or authorization.
403	APIForbiddenError The server understood the request, but is refusing to fulfill it. Authorization will not help and the request should not be repeated.
404	APINotFoundError The server hasn't found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
405	APIMethodNotAllowedError The method specified in the Request-Line isn't allowed for the resource identified by the Request-URI. The Compute Classic API supports only a subset of HTTP methods (GET, POST, PUT, DELETE). And not all methods are supported for all objects. This exception will be thrown if an unsupported method is invoked.
406	APINotAcceptableError The resource 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.
409	APIConflictError The request could not be completed due to a conflict with the current state of the resource, or, in the case of a resource-creation call, the requested resource already exists in the system. You can either delete the existing object and create it afresh or create a new object with a unique identifier.
410	APIGoneError The requested resource no longer exists on the server. For example, where an instance once existed, but is no longer running, a duplicate of this instance with the same identifier can't be created.
412	APIPreconditionFailedError When a GET or PUT request is sent to a VPN endpoint and the VPN gateway, the gateway in your data center through which you want to connect to the Oracle Cloud VPN gateway, has not been configured or is disabled.
413	APIRequestTooLarge The image uploaded exceeds the maximum allowed upload size.
415	APIUnsupportedTypeError The server cannot service the request as the requested entity is specified in a format which is not supported by the requested resource for the requested method. This usually indicates a JSON encoding error.
429	APITooManyRequestsError The server cannot service this request as the number of requests raised has exceeded the specified limit. There is a limit on the number of requests that the server can handle. This limitation varies depending on the resource and the action that you want to perform. For example, there is a limit on the number of screen capture requests you can raise per instance per minute.
5xx	APIServerError An internal error has occurred and the server is incapable of fulfilling the request.
500	APIUncaughtExceptionError The server encountered an unexpected condition that prevented it from fulfilling the request. This error will return a reference code which you must note and supply when you contact Oracle Support.
501	APINotImplementedError The server does not currently support the functionality required to fulfill the request.
503	APIServiceUnavailable The server is currently unable to handle the request due to temporary overloading or maintenance. This is most likely a load-related condition, which should be alleviated after a short delay.
502/504	APIGatewayError The connection between the API and the service layer of Oracle Single-Tenant Compute Cloud Service is down. This is generally a temporary, most likely service failover-related, condition, which should be alleviated after a short delay.
507	APIInsufficientStorage The server is unable to store the representation needed to successfully complete the request. This condition is considered to be temporary.