Errors

In this guide, we will talk about what happens when something goes wrong while you work with the API. Mistakes happen, and mostly they will be yours, not ours. Let's look at some status codes and error types you might encounter.

You can tell if your request was successful by checking the status code when receiving an API response. If a response comes back unsuccessful, you can use the error type and error message to figure out what has gone wrong and do some rudimentary debugging (before contacting support).

Before reaching out to support with an error, please be aware that most reported errors are typically due to incorrect API usage or invalid parameters. Therefore, please carefully check your code and request parameters before contacting Aella support.

Status codes

Here is a list of the different categories of status codes returned by the Aella for Merchants API. Use these to understand if a request was successful.

Name
2xx
Description
A 2xx status code indicates a successful response.
Name
4xx
Description
A 4xx status code indicates a client error — this means it's a you problem.
Name
5xx
Description
A 5xx status code indicates a server error — you won't be seeing these.

Error types

Whenever a request is unsuccessful, the Aella for Merchants API will return an error response with an error type and message. You can use this information to understand better what has gone wrong and how to fix it. Most of the error messages are helpful and actionable.

Here is a list of the common error types returned by the Aella API — use these to understand what has gone wrong.

Name
api_error
Description
This means that we made an error, which is highly speculative and unlikely.
Name
invalid_request
Description
This means that you made an error, which is much more likely.

Error response

{
  "status": false,
  "message": "Invalid account number provided",
  "code": "INVALID_ACCOUNT_NUMBER",
  "data": null
}