HTTP Status Codes

The MC API uses standard HTTP status codes in response to indicate the success or failure of the request. Unless stated otherwise in the description of an operation, the following general interpretations of the status code values apply.

Table 1. HTTP Status Codes
HTTP Status Code HTTP Status Message Description
200 OK The request has succeeded completely. A response body is provided that contains the results of the request.
204 No Content The request succeeded completely, and no additional response information is provided.
400 Bad Request The request was missing required input, had errors in the provided input, or included extraneous input. Additional information regarding the error is provided in an error response body that includes a reason code with additional information.
403 Forbidden Multiple error conditions result in this status code:
  • The request requires authentication but no X-API-Session header was provided, or one was provided but the session ID was invalid.
  • The user under which the API request was authenticated is not authorized to perform the requested operation.
404 Not Found Multiple error conditions result in this status code:
  • The URI does not designate an extant resource, or designates a resource for which the API user does not have object-access permission.
  • The URI designates a resource or operation that is not supported by the MC because it is currently the alternate MC.
405 Method Not Allowed The request specifies an HTTP method that is not valid for the designated URI.
409 Conflict The managed resource is in an incorrect state (status) for performing the requested operation. Additional information regarding the error is provided in an error response body that includes a reason code with additional information.
412 Resource Modified Precondition Failed. If client supplied ETag and server ETag match then proceed with POST. Otherwise results in 412 resource modified error.
413 Request Body Too Large The request includes a request body that is too large.
415 Unsupported Media Type The Content-Type header for the request specifies a representation that is not supported by the Web Services API.
500 Internal Server Error A server error occurred during processing of the request.
501 Not Implemented The request specifies an HTTP method that is not recognized by the server (for any resource).
503 Service Unavailable The request could not be carried out by the MC due to some temporary condition.
505 HTTP Version Not Supported The request specifies an HTTP protocol version that is not supported by the Web Services API.