Skip to main content

Introduction

This document describes the shape of Chift errors and lists the errors 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:

Specific errors

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

List of errors

Sync errors

Syncs raise error codes prefixed with ERROR_SYNC_. These errors appear in the execution logs of a sync. See Monitor executions to find the execution logs and the affected records. Errors specific to the invoices sync (ERROR_SYNC_INVOICE_*) are listed in the Invoices sync troubleshooting section.