401 · Missing or invalid API key
401 · Missing or invalid API key
Confirm the
Authorization: Bearer ... header, the environment, and that the key contains no spaces or line breaks.409 · Resource already exists or a condition is not met
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.422 · Payload validation
422 · Payload validation
Review field names, types, allowed values, and the difference between omission,
null, and an empty string.409 · The leader history is not ready for subscriptions
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 forCOMPLETED.HISTORY_SYNC_FAILED: correcterror_messageand request synchronization again.HISTORY_SYNC_REQUIRED: the required import was canceled; request it again.
required_before_subscription to bypass an import that your integration marked as required.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, oroperation_id. - Redacted payload.

