> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Error codes

> Axottle API HTTP statuses, typical reasons and operator actions.

All endpoints live under `/api/v1` and, except for public and setup endpoints, require an authorized admin session.

> [!NOTE]
>
> For whom: Administrator, SRE, Integration Developer, Rights Required: Depending on Endpoint.

> [!NOTE]
>
> The full machine catalog of error codes in the product has not yet been published. This table describes the **observed behavior of API**: which HTTP statuses return, in what situations and what to do for the operator. As the directory stabilizes, the page will expand.

## HTTP Statuses

| Status | Typical cause | Operator Action | |
| - | - | - | - |
| `400` | Incorrect request: invalid JSON, missing mandatory fields, incorrect parameters | Check the body and query parameters according to the documentation of the corresponding endpoint | |
| `401` | No session or session expired: no/uninvalid `Authorization: Bearer <session-token>` | header Complete login again (`POST /api/v1/auth/login`) and repeat the request with the new | token |
| `403` | Insufficient permissions | Check the account permissions required for the requested action | |
| `404` | Resource not found: a non-existent identifier, a remote object or an incorrect public token in public links | Check the identifier / token in the URL; for public links – the relevance of the | link |
| `409` | Status conflict: operation is incompatible with the current state of the | system Wait for the completion of a competing operation or eliminate the conflict (examples below) | |
| `422` | Validation error: data is syntactically correct, but does not pass business verification | Correct field values according to the error message | |
| `5xx` | Internal panel or dependent service error | See logs: `axottle logs backend --tail 200`, then `axottle doctor`; when repeated, collect support band | |

## Examples of `409` conflicts

* **Backup is already executed by** - no more than one run is running for each profile at the same time; a repeat `POST /api/v1/backups/runs` for the same profile will return `409`. Wait for the current launch to complete.
* **Remnawave auto-binding disabled** - `POST /api/v1/setup/remnawave/bootstrap` returns `409` if the `AXOTTLE_RW_BOOTSTRAP` variable is not enabled.
* **Second session of the Telegram assistant** Helper session to configure notifications single; parallel attempt to open the second receives `409`.

## Special cases

### Test of Telegram notifications

`POST /api/v1/notifications/telegram/test` is the only notification endpoint that returns a real delivery error.

| Status | Value | Action | |
| - | - | - | - |
| `400` | Notifications not configured (no bot token or chat id) | Fill in the Telegram settings in the | panel |
| `502` | Telegram Bot API error | Check the correctness of the bot token and the rights of the bot in the chat | |
| `504` | Call timeout to Telegram | Check outbound network availability from the | panel server |

In other cases, the delivery of notifications is best-effort: the failure of sending does not break the operation that caused it, the error is recorded in the audit log.

## Diagnosis by step

**1. Determine the error class**

`4xx` is a request, rights, or state problem; `5xx` is a panel-side problem.

**2. For 401/403, check the session and account permissions**

Sign in again and check the permissions required for the requested action.

**3. For 5xx see Logistics and Doctor**

```bash theme={null}
axottle logs backend --tail 200
axottle doctor
```

## Related pages

> [card] [CLI axottle](https://docs.axottle.com/en/reference/cli.md)
>
> Teams `logs`, `doctor`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.