HTTP status codes
Responses
Cryptonly 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
200 OK
Standard response for successful HTTP requests
201 Created
The request has been fulfilled, resulting in the creation of a new resource
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 use an api key correctly
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 orderId value you are trying to use had been used before
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
Common invoice error codes
Some 400 Bad Request responses include a machine-readable code in the JSON body. Common invoice-related codes:
exceptions.invoice.depositAlreadyActive
A deposit is already active for this invoice (for example customer already selected a currency)
exceptions.invoice.noActiveDeposit
No active deposit exists for the requested operation
See the Cryptonly SDK merchant-api-codes constants for the full list.
Last updated