Account Lifecycle
Create, update, and disable MT5 accounts while keeping CRM, KYC, and broker data in sync.
MANAGER API
MT5 Manager API
Administrative MT5 surface for user management, balances, instrument metadata, access policies, and reporting pipelines.
Scope
Broker operations
Coverage
Users, balances, symbols, reports
Best fit
Modern MT5 back-office stacks
Funding & Credit
Drive deposits, withdrawals, credits, and operator-reviewed corrections through audited workflows.
Reporting Surface
Expose group activity, exposure, and daily operational summaries to finance and compliance teams.
Quick Start
MT5 Manager endpoints are ideal when your product needs broker-level control without coupling directly to the MetaTrader terminal layer.
Build declarative workflows around user creation, funding, permissions, and daily reporting.
BASH
curl https://api.metatraderapi.xyz/mt5/manager/accounts/128001 \
-H "Authorization: Bearer <manager-key>" \
-H "Accept: application/json"Account Lifecycle
Create accounts, rotate passwords, change leverage, assign groups, and query current permissions from one management plane.
These flows are commonly wired into onboarding portals and broker CRM systems.
Deposits, Withdrawals, and Credits
Balance operations support operator metadata, comments, idempotency-safe wrappers, and downstream accounting sync.
Operational Reporting
Use report endpoints to collect daily account states, group utilization, exposure, and instrument activity for finance and compliance teams.
Authentication & Headers
Use a scoped MT5 manager credential for automation and isolate it from human operator accounts.
Long-running reporting workers should use read-only credentials wherever possible, while financial operations stay on separately monitored keys.
| Header | Value | Use | Description |
|---|---|---|---|
| Authorization | Bearer <manager-key> | Required | Scoped MT5 manager credential. |
| x-operator-id | backoffice-reporting | Recommended | Operator or workflow id used in audit records. |
| x-request-id | req_mng5_7711 | Recommended | Idempotency key for retry-safe mutations. |
| x-environment | production | Optional | Environment marker for multi-tenant control planes. |
Endpoint Matrix
Accounts & Access
| Method | Path | Purpose |
|---|---|---|
| POST | /accounts | Create a new MT5 trading account. |
| PATCH | /accounts/{login} | Adjust leverage, permissions, or group assignment. |
| GET | /accounts/{login} | Read account lifecycle state and metadata. |
| POST | /accounts/{login}/password | Rotate investor or trading passwords. |
Funding & Transactions
| Method | Path | Purpose |
|---|---|---|
| POST | /transactions/deposit | Deposit funds into a client account. |
| POST | /transactions/withdraw | Withdraw balance with operator context. |
| POST | /transactions/credit | Add broker credit or promotions. |
| GET | /transactions/history | Review the funding ledger for reconciliation. |
Reports & Oversight
| Method | Path | Purpose |
|---|---|---|
| GET | /reports/daily | Return the daily operational report. |
| GET | /reports/groups | Aggregate balance and exposure by group. |
| GET | /reports/symbols | Inspect instrument activity and volume. |
| GET | /reports/exposure | Read net exposure and margin distribution. |
Errors & Limits
MT5 manager automations often sit on the boundary between finance, CRM, and compliance systems. Treat failures as workflow events rather than raw HTTP retries.
The safest pattern is request id + audit log + human escalation for sensitive operations such as leverage changes, password resets, or funding corrections.
| Code | Name | Meaning |
|---|---|---|
| 400 | ValidationError | The requested group, leverage, or balance payload is invalid. |
| 401 | Unauthorized | Manager credential is missing or does not have scope for the action. |
| 403 | PermissionDenied | The service account cannot perform the requested broker operation. |
| 409 | AlreadyApplied | The requested balance or account mutation was already applied. |
| 503 | ManagerOffline | The management plane is temporarily unavailable. |
Deployment & Runtime
Route read-heavy reporting through dedicated workers and separate them from onboarding or finance queues.
Where possible, mirror daily report payloads into your data warehouse instead of rebuilding them from raw operational reads.
- Create isolated service accounts for reporting and finance.
- Attach request ids to every balance mutation.
- Store operator metadata together with each response payload.
- Trigger alerts when report freshness or queue lag drifts out of range.