Errors

As stated earlier, Redstone's API is RESTful and as such, uses conventional HTTP response codes to indicate the success or failure of requests.

Status Code	Description
200, 201	The request was successful and intended action was carried out.
400	The request could not be fulfilled because it already exists or is a bad request
401	The request was not authorized. This occurs when you fail to pass in a private key in the authorization header or the one passed in is invalid.
404	The request could not be fulfilled as the request resource does not exist.
500, 501, 502, 503, 504	The request could not be fulfilled due to an error on Redstone's end. This shouldn't happen so please report as soon as you encounter any instance of this.

Failure Reasons

This section lists all possible failure reasons returned by the API, along with their descriptions and corresponding status values. Use these codes to understand and handle failed transaction responses.

Failure Reason	Description	Status
ABANDONED_TRANSACTION	Abandoned transaction/PIN not inputted	Failed
DECLINED_TRANSACTION	Declined transaction	Failed
INSUFFICIENT_FUNDS	Insufficient Wallet Balance	Failed
INVALID_PIN	PIN Mismatch	Failed
TRANSACTION_LIMIT_EXCEEDED	Transaction Limit Exceeded	Failed
ACCOUNT_NOT_FOUND	Invalid Wallet Account	Failed
ACCOUNT_BLOCKED	Wallet Locked / Suspended	Failed
PROVIDER_TIMEOUT	Provider System Timeout	Failed
TRNASACTION_FAILED	Transaction failed on the provider’s end	Failed
TRNASACTION_PENDING	Transaction was still pending on the provider's end	Pending