Errors

​

Introduction

This document describes how you can expect chift errors and list as well the errors that you can expect from our different APIs.

​

Chift Error

A chift error is always composed of the following elements:

• status: “error”
• message: “message explaining the error”
• error_code: “unique error code to describe the error”
• detail: “additional details explaining the error” (optional)

The errors are always returned with an HTTP error code (4XX, 5XX). Note that the combination of the message and the error_code is not always unique.

Example of an error message:

{
    "message": "The resource GET - /order is not supported by Cashpad",
    "status": "error",
    "error_code": "ERROR_RESOURCE_NOT_SUPPORTED"
}

​

Specific errors

Even if it’s the goal to only use generic errors whenever possible, there are use case where the raised errors are specific to the connectors. In such case, those errors are described in the related connector documentation.

​

List of errors