Error Handling

Catenda uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted), and codes in the 5xx range indicate a system error that cannot be resolved by the user.

Error responses are JSON objects comprised of a code and a message. The code is the numerical error code of the error and the message contains a human-readable message describing the error.

400 Bad Request

Code

Description

23

The uploaded file is empty

24

Incorrect field or content in the request

102

Viewer token provided is invalid

401 Unauthorized

Code

Description

10

The access token is missing

11

The access token provided is empty or invalid

12

The access token provided has expired

403 Forbidden

Code

Description

21

Forbidden action

100

Insufficient privilege for action

101

Maximum number of projects for organization reached

404 Not Found

Code

Description

20

Couldn't find the specified resource

409 Conflict

Code

Description

25

Action is incompatible with the specified resource

600

Action is incompatible with the specified custom field

422 Unprocessable Content

Code

Description

22

Input provided is incompatible

500 Internal Server Error

Code

Description

30

Error occurred on the server

103

Multi-factor authorization required



Updated 14 Jun 2024
Did this page help you?