Comment on page
Responses
Cryptopay API operates HTTP status codes to indicate the status of user’s requests including both successful and unsuccessful responses.
Responses will also include JSON-formatted data for further details:
- 1xx (Informational): The request is received, continuing process
- 2xx (Successful): The request is successfully received, understood, and accepted
- 3xx (Redirection): Further action needs to be taken in order to complete the request
- 4xx (Client Error): The request contains bad syntax or cannot be fulfilled
- 5xx (Server Error): The server failed to fulfil an apparently valid request
Status code | Meaning |
200 OK | Standard response for successful HTTP requests |
201 Created | The request has been fulfilled, resulting in the creation of a new resource |
202 Accepted | The request has been accepted for processing, but the processing has not been completed |
204 No Content | The server successfully processed the request and is not returning any content |
304 Not Modified | Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match |
400 Bad Request | The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing) |
401 Unauthorized | Most likely you weren't able to construct and sign your API request correctly using HMAC |
403 Forbidden | You don't have required permissions to perform requested action on the resource. Check your API key whitelist |
404 Not Found | We don't have the resource you've requested |
409 Conflict | Most likely the custom_id value you are trying to use had been used before |
422 Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic errors |
429 API rate limit exceeded | Amount API requests for api_key exceeded 200 requests per minute |
500 Internal Server Error | We have a problem with our server |
503 Service Unavailable | We are temporarily offline for maintenance |
Last modified 2yr ago