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

# Common errors

> Safely diagnose common responses during integration.

> [accordion] 401 · Missing or invalid API key
>
> Confirm the `Authorization: Bearer ...` header, the environment, and that the key contains no spaces or line breaks.

> [accordion] 409 · Resource already exists or a condition is not met
>
> Read `detail`. It may indicate an already registered account, an active allocation for the same pair, a reached limit, insufficient deposit, or non-withdrawable funds.

> [accordion] 422 · Payload validation
>
> Review field names, types, allowed values, and the difference between omission, `null`, and an empty string.

> [accordion] 409 · The leader history is not ready for subscriptions
>
> Call `GET /api/v1/mam/accounts/{account_login}/history-sync` using the leader login.
>
> * `HISTORY_SYNC_IN_PROGRESS`: wait for `COMPLETED`.
> * `HISTORY_SYNC_FAILED`: correct `error_message` and request synchronization again.
> * `HISTORY_SYNC_REQUIRED`: the required import was canceled; request it again.
>
> Do not disable `required_before_subscription` to bypass an import that your integration marked as required.

> [accordion] 502 · MT5 operation unavailable
>
> Preserve the same `idempotency_key`, apply backoff, and record `X-Request-ID`. Do not assume that a financial operation failed without retrieving its status.

## Information for support

Share only:

* UTC date and time.
* Method and path, without API keys or credentials.
* HTTP code and `request_id`.
* Applicable `mt5_login`, `leader_id`, `allocation_id`, or `operation_id`.
* Redacted payload.

> [!WARNING]
>
> Do not send MT5 passwords, API keys, `signing_secret`, or unredacted webhook bodies.


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