Error types

Bond organizes errors and error codes into high level groups called types. These error types are useful because each type suggests a different method of tracing the origin of the problem.

📘

Note

Some error types are not provided by the Bond platform and we have no specific information regarding these types.

Request error

Cause: These errors relate to a request to a server.
Resolution: Fix the issue with the request that is detailed in the error message.
Request errors can be resolved by the end user.

An example of a request error is shown below.

POST /api/v0/core/transfer
{
    "Message": "Missing Required Field(s): 'amount'", 
    "Status": 400, 
    "Code": "create_transfer_schema", 
    "Type": "Request Error",
}

Server error

Cause: These errors relate to issues with Bond's internal servers.
Resolution: Contact Bond support.
As these errors can result in significant customer issues, contact our support team as soon as possible.

An example of a server error is shown below.

POST /api/v0/core/transfer
{
   "Message": "Could not create Transfer. Contact Support",
   "Status": 500,
   "Code": "unknown_create_transfer",
   "Type": "Server Error",
}

Process error

Cause: These errors relate to the execution of a process at the backend.
Resolution: Contact Bond support.
As these errors may take longer to resolve than server errors, contact our support team as soon as possible.

An example of a process error is shown below.

POST /api/v0/core/transfer
{
    "Message": "Service has been disabled. Contact Support",
    "Status": 424,
    "Code": "service_disabled",
    "Type": "Process Error",
 }