API Response Errors
HTTP status codes do not always provide sufficient information about the cause of an error. For more detailed programmatic handling of errors, responses contain additional JSON fields that describe the error.
Error format
Whenever an API request results in an error, the response will contain both a high-level error class specified by the code
and a human-readable summary in the message
.
{"code":2,"message":"Request body contains unprocessable entity."}
Extended error format
In some cases there is extended information available for clients about why a request has failed. For example, failing to supply a value for a required field1 will result in the following error:
{"code":2,"message":"Invalid entity.
metadata.email may not be empty (was null)","errors":[{"error":"invalid_value","location":"metadata.email","message":"metadata.email may not be empty (was null)"}]}
List of API Error Codes
The table below shows the list of error codes that may be returned in an API error response.
Code | Message | Description |
---|---|---|
-1 | Unknown Error | An unknown error occurred processing the API request |
1 | Malformed authorization. Is the authorization type missing? | API Key is missing or malformed |
2 | Invalid Entity | Error with the JSON object passed in the request body |
3 | Forbidden | API Key used with request does not have one of the roles authorized to call the API endpoint |
5 | Too many requests | Rate limit exceeded |
2003 | The recipient address already exists | The blockchain address has already been associated with the account |
2004 | The address is not a verified withdrawal address | The blockchain address must first be verified before it can be used as a destination in a transfer request |
2005 | The address belongs to an unsupported blockchain | The blockchain type used as a transfer destination is not supported |
2006 | Wallet type is not supported | The wallet type specified when creating an end user wallet is not supported |
2007 | Unsupported transfer | A transfer from the provided source to the provided destination is not supported |
5000 | Invalid travel rule identity type | The provided identity type must be either "individual" or "business" |
5001 | Payout does not found | Payout doesn’t exist based on the ID provided. Please check the payout id |
5002 | Invalid payout amount | Payout amount must be more than 0 |
5003 | Inactive destination address | Cannot send payout to an inactive destination address. If you have just added the address, you may have to wait for 24 hours before use |
5004 | Destination address not found | The destination address for this payout could not be found |
5005 | Source wallet not found | Source wallet for this payout could not be found |
5006 | Insufficient funds | The source wallet has insufficient funds for this payout |
5007 | Unsupported currency | currency not currently supported for this operation |
5011 | Invalid destination address | cannot send payout to an invalid destination address |
5012 | Invalid destination location types | cannot search for both crypto and fiat payouts |
5013 | Invalid source wallet id | source wallet id must be a number for payouts search |
5014 | The address is not valid for the blockchain | Provided blockchain address is not valid for the corresponding blockchain |
5015 | Invalid destination chain | Provided blockchain address has an invalid chain in respect to the currency used |
Updated about 1 month ago