Errors
HTTP status code summary
Customer uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a create failed, etc.). C Codes in the 5xx range indicate an error with customer servers (these are rare).
Some 4xx errors that could be handled programmatically (e.g., a create customer fail) include an error code that briefly explains the error reported.
200 - OK
Everything worked as expected.
400 - Bad Request
The request was unacceptable, often due to missing a required parameter.
401 - Unauthorized
No valid API key provided.
402 - Request Failed
The parameters were valid but the request failed.
404 - Not Found
The requested resource doesn’t exist.
409 - Conflict
The request conflicts with another request (perhaps due to using the same idempotent key).
429 - Too Many Requests
Too many requests hit the API too quickly. We recommend an exponential backoff of your requests.
500, 502, 503, 504
Server ErrorsSomething went wrong on customer’s end. (These are rare.)
Errors types
Error typesError codes
Error codesGood to know: Please find all API commands below, starting with 700 – Start Credit Card charge (3DS Enabled)
Last updated