Skip to main content

​
Create an MT5 account

Use POST /api/v1/mam/accounts/create when the account does not yet exist. platform_group must be the actual MT5 group assigned by the broker.
The response returns mt5_login and the generated credentials. Deliver them through a secure channel and do not record them in plain text.
The MT5 permission profiles supported by this integration are 9073 for trading enabled and 8981 to apply Trade Disabled. Send one of these values explicitly.

​
Register an existing account

Use POST /api/v1/mam/accounts/add. This endpoint registers the account in MAM; it does not create the account or change its MT5 permissions. When you register an existing account as a leader (can_be_leader=true), the platform automatically imports its previous MT5 trades. This makes its metrics and historical results available from the start. The account can be retrieved and edited during the import, but it cannot receive new subscribers until history synchronization is complete.
If the account is registered only as a follower (can_be_leader=false), it does not require a history import and becomes available immediately.
If you later enable a follower account to act as a leader through PATCH /api/v1/mam/accounts/{account_login}, the history import starts automatically at that time. Editing an account that was already a leader does not import its history again. See the history synchronization guide to review progress or repeat the process manually.

​
Available synchronization operations

Balance movement synchronization accepts lookback_hours from 1 to 2160, or a from_at/to_at interval. It is idempotent per MT5 deal: a second run skips movements that have already been recorded.

​
Fund and withdraw

Financial operations require a stable idempotency_key:
  • Deposit: POST /api/v1/mam/accounts/{account_login}/deposit
  • Withdrawal: POST /api/v1/mam/accounts/{account_login}/withdraw
  • Audit: GET /api/v1/mam/accounts/{account_login}/balance-transactions
Use sync-mt5 for controlled reconciliation of external movements. New operations must go through the deposit and withdrawal endpoints to preserve idempotency and traceability.
A follower withdrawal first charges any accrued performance fee. Withdrawing a leader’s PAYMENT balance uses a different endpoint.

​
Batch queries

To avoid long query strings, POST /api/v1/mam/accounts/query accepts up to 1,000 logins in the body and preserves the semantics of the general listing endpoint.

​
Copy-trading requirements

  • Status ACTIVE.
  • account_mode="HEDGING".
  • can_be_leader=true to originate trades.
  • can_be_follower=true to receive trades.
Last modified on August 24, 2026