Skip to content

Handling errors

Handling errors with the Djamo Business API

Convention

The Djamo Business API uses conventional HTTP response codes to indicate the success or failure of an API request.

In general :

✅ 2xx

Codes in this range indicate that the request was well received and being processed.

❌ 4xx

Codes in this range indicate some king of error with your input (like authentication or validation error).

❌ 5xx

Codes in this range indicate a server error of some sort. These should be rare. If persistent, you should contact Djamo's tech support team.

HTTP errors

Please find below a list of HTTP errors that we return at the moment.

HTTP code Description
401 The request could not be authenticated. The API Key is either missing or is incorrect.
403 The API Key is not allowed to access the resource.
404 The ressource could not be found.
409 A collision happened. For example you used the same reference twice to create two different transactions.
429 The rate limit was exceeded. The server received too many requests in a given period of time.
500 A server error occured. If this persists, please contact Djamo.

Note

Note that these only indicate the status of the HTTP request and not any transactions status.