Response Codes and Statuses

 REST API - RESPONSE CODES AND STATUSES

200(OK)

The request was successfully completed.

201(Created)

A new resource was successfully created.

204(No content)

Usually sent out in response to a PUT, POST, or DELETE request when the REST API declines to send back any status message or representation in the response message’s body.

301(Moved Permanently)

Indicates that the REST API’s resource model has been significantly redesigned, and a new permanent URI has been assigned to the client’s requested resource.

302(Found)

Indicates that the resource requested has been temporarily moved to the URL given by the Location header.

304(Not Modified)

Indicates that the requested resource has not been modified since the previous transmission.

307(Temporary Redirect)

Indicates that the resource requested has been temporarily moved to the URL given by the Location headers. The method and the body of the original request are reused to perform the redirected request.

400(Bad Request)

The request was invalid.

401(Unauthorized)

The request did not include an authentication token, or the authentication token was expired.

403(Forbidden)

The client did not have permission to access the requested resource.

404(Not Found)

The request resource was not found.

405(Method Not Allowed)

The HTTP method in the request was not supported by the resource.

409(Conflict)

The request could not be completed due to a conflict. For example, POST Admin folder API cannot be complete if the given file or folder name already exists in the parent location.

412(Precondition Failed)

Indicates that access to the target resource has been denied.

500(Internal Server Error)

The request was not completed due to an internal error on the server side.

502(Bad Gateway)

Indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.

503(Service Unavailable)

The server was unavailable.