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 charge failed, etc.). Codes in the 5xx range indicate an error with our servers.
The following success and error codes are managed by our APIs:
Success
|
Status code |
HTTP Message |
Description |
|---|---|---|
|
200 |
OK |
Everything worked as expected. |
|
201 |
Created |
Resource has been created successfully |
|
204 |
No Content |
Server has successfully handled the request and that there is no additional content to send in the response |
Error
|
Status code |
HTTP Message |
Description |
|---|---|---|
|
400 |
Bad Request |
The request was unacceptable, often due to missing a required parameter. |
|
401 |
Unauthorized |
No valid Authentication provided. |
|
403 |
Forbidden |
You don't have permissions to perform the request. |
|
404 |
Not Found |
The requested resource doesn't exist. |
|
406 |
Not Acceptable |
Provided content-type header is invalid |
|
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. |
|
500, 502, 503, 504 |
Server Errors |
Something went wrong on our API server. |
You can find more about HTTP protocol in the RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content document.