REST API for Session Delivery Manager Release 8.1

Status Codes

When you call any of the REST API for Oracle? Communications Session Delivery Manager resources, the Response header returns one of the standard HTTP/HTTPS status codes that appear in the message and defined in the following table:

HTTP Status Code Description

HTTP Status Code	Description
`200 (OK)`	The request was successfully completed. A 200 status is returned for a successful GET, PUT or POST request method. For example, in a GET request, the response contains an entity corresponding to the requested resource and in a POST request, the response contains an entity describing or containing the result of the action.
`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
`204 (No Content)`	The server successfully processed the request, but is not returning any content. This code is usually used as a response to a successful delete request.

200 (OK)

The request was successfully completed. A 200 status is returned for a successful GET, PUT or POST request method.

For example, in a GET request, the response contains an entity corresponding to the requested resource and in a POST request, the response contains an entity describing or containing the result of the action.

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

204 (No Content) The server successfully processed the request, but is not returning any content. This code is usually used as a response to a successful delete request.