HTTP Response Codes

HTTP Request

CPX uses HTTP response status codes to indicate the success or failure of your API requests. If your request fails, CPX returns an error using the appropriate status code.

In general, there are three status code ranges you can expect:

HTTP Response	Meaning
202 Accepted	status code indicates that the request has been accepted for process
204 No Content	success status response code indicates that the request has succeeded,
400 Bad Request	response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error
401 Unauthorized	client error status response code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.
403 Forbidden	client error status response code indicates that the server understood the request but refuses to authorize it
404 Not Found	standard response code to indicate that communication with a given server was successful, but the server could not find what was requested.
405 Method Not Allowed	response status code indicates that the request method is known by the server but is not supported by the target resource.
406 Not Acceptable	client error response code indicates that the server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers, and that the server is unwilling to supply a default representation.
422 Unprocessable Entity	response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.
503 Service Unavailable	server error response code indicates that the server is not ready to handle the request.
500 Internal Server Error	The server encountered an error while processing your request and failed.