Status Codes

Table 1 lists the status codes that may be returned when you call MPC APIs.

**Table 1** Status codes
Status Code	Description
200 OK	The request has succeeded.
201 Created	The request has been fulfilled and resulted in a new resource being created.
202 Accepted	The request has been accepted for processing, but the processing has not been completed.
204 No Content	The request has been fulfilled, but the HTTP response does not contain a response body.
400 Bad Request	The request could not be understood by the server. The client should not repeat the request without modifications.
401 Unauthorized	The authentication information provided by the client is incorrect or invalid.
403 Forbidden	The server understood the request, but is refusing to fulfill it. The client should not repeat the request without modifications.
404 Not Found	The requested resource could not be found. The client should not repeat the request without modifications.
405 Method Not Allowed	The method specified in the request is not supported for the requested resource. The client should not repeat the request without modifications.
406 Not Acceptable	The server could not fulfill the request according to the content characteristics of the request.
407 Proxy Authentication Required	This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
408 Request Timeout	The client did not produce a request within the time that the server was prepared to wait. The client may repeat the request without modifications at any later time.
409 Conflict	The request could not be completed due to a conflict with the current state of the resource. This status code indicates that the resource that the client is attempting to create already exists, or that the request has failed to be processed because of the update of the conflict request.
500 Internal Server Error	The server is able to receive the request but unable to understand it.
501 Not Implemented	The server does not support the functionality required to fulfill the request.
502 Bad Gateway	The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
503 Service Unavailable	The server is currently unable to handle the request. The client should not repeat the request without modifications.
504 Gateway Timeout	A gateway timeout error occurred.