Our API Endpoints use conventional HTTP response codes to indicate the success or failure of an API request.
General error codes
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 charge failed, etc.), and codes in the 5xx range indicate an error with our backend (these are rare).
Http Status Code
Message
Possible Payload
200
Ok
Request was successful and contains the response content
202
Accepted
The request has been accepted for processing, but the processing has not been completed
203
Non-Authoritative Information
Request was successful but contains business errors
400
Bad Request
The Request was incorrect (due to http protocol)
401
Unauthorized
Not authorized access to a endpoint
403
Forbidden
Not authorized access to a specific resource
404
Not Found
Resource not found
409
Conflict
Resource already exists
500
Internal Server Error
Unexpected Server Error
501
Not implemented
Method not implemented
Specific error codes
Not all errors map cleanly onto HTTP response codes, however. When a request is valid but does not complete successfully, we return a specific Error code.