Errors

Overview

While using the SDK, you may run into an error. Usually, this is caused by an invalid parameter in your implementation.

Here is an example of one error you may run into:

{ 
    "httpStatusCode": 401,
    "message": "Invalid destination provided",
    "info": { "unknowns": [ "moffdd" ] } 
}

This sections explains the error format and messages utilized by Connect.

API Error responses

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.

{
   "message":"Insufficient funds."
}

 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:

{ 
    "httpStatusCode": 401,
    "message": "Invalid destination provided",
    "info": { "unknowns": [ "moffdd" ] } 
}

List of API Error Codes