Errors

HTTP Status Codes

Our API 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 request failed, etc.)
• Codes in the 5xx range indicate an error with our servers (these are rare)

Some 4xx errors that could be handled programmatically include an error code that briefly explains the error reported.

Status Code Reference

Code	Status	Description
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
403	Forbidden	The API key doesn’t have permissions to perform the request
404	Not Found	The requested resource doesn’t exist
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 Errors	Something went wrong on our end.

Attributes

Attribute	Type	Description
code	nullable string	For some errors that could be handled programmatically, a short string indicating the error code reported.
message	nullable string	A human-readable message providing more details about the error. For card errors, these messages can be shown to your users.
details	nullable object	Additional information about the error, such as which parameters caused it.