MT5 Manager API integration.

1. 1EventKYC provider: verification passed
2. 2CRM recordClient status → Approved; segment read
3. 3Integration layerJob queued · idempotency key per client
4. 4Manager APIUserAdd
5. 5MT5 serverLive account created in segment group

1. 1EventPSP callback: transaction settled
2. 2CRM recordDeposit record matched to account
3. 3Integration layerIdempotency key = PSP transaction ID
4. 4Manager APIDealerBalance
5. 5MT5 serverBalance operation with comment reference

1. 1EventCheckout: challenge purchased
2. 2CRM recordChallenge record with phase rules
3. 3Integration layerProvisioning job · phase config attached
4. 4Manager APIUserAdd
5. 5MT5 serverEvaluation account in Phase 1 group

1. 1EventRule engine: phase target met
2. 2CRM recordChallenge state → Passed
3. 3Integration layerState check before write
4. 4Manager APIUserUpdate
5. 5MT5 serverAccount moved to next-phase group

1. 1EventTrader: payout requested
2. 2CRM recordPayout record → Pending review
3. 3Integration layerReads only until approved
4. 4Manager APIUserGet · DealRequest
5. 5MT5 serverEquity and deal history returned

Human approval before any balance write

Connection sequence · C# (.NET wrapper)

1. 01

   Load the SDK and create a manager

   The MetaQuotes Manager API ships as native DLLs with a .NET wrapper. The factory loads the library and checks the API version before any manager interface is created.

   using MetaQuotes.MT5CommonAPI;
   using MetaQuotes.MT5ManagerAPI;
   
   MTRetCode res = SMTManagerAPIFactory.Initialize(sdkPath);
   if (res != MTRetCode.MT_RET_OK) throw new Exception($"Init: {res}");
   
   CIMTManagerAPI manager =
       SMTManagerAPIFactory.CreateManager(SMTManagerAPIFactory.ManagerAPIVersion, out res);

2. 02

   Connect with a dedicated manager login

   Use a manager account created for the integration, with only the permissions it needs. Pump mode controls which data the server streams to the client.

   res = manager.Connect(
       server,            // "access.example:443"
       managerLogin,      // dedicated integration login
       password,          // from a secret store, never in code
       null,
       CIMTManagerAPI.EnPumpModes.PUMP_MODE_USERS
         | CIMTManagerAPI.EnPumpModes.PUMP_MODE_POSITIONS,
       30000);            // timeout, ms

3. 03

   Run one controlled operation

   Each business event maps to one API call, wrapped with an idempotency key and a return-code check. Failures are retried or escalated, never silently ignored.

   if (res != MTRetCode.MT_RET_OK)
       logger.Error($"Connect failed: {res}");

4. 04

   Write back, disconnect and release

   The resulting login, deal ticket or return code is written to the CRM record with an audit entry. Interfaces are released when the worker shuts down.

   manager.Disconnect();
   manager.Release();
   SMTManagerAPIFactory.Shutdown();

Command reference · CIMTManagerAPI

CIMTUser user = manager.UserCreate();
user.Group("real\\standard-usd");
user.Name(client.FullName);
user.Leverage(100);
res = manager.UserAdd(user, masterPass, investorPass);
ulong login = user.Login();      // write back to CRM

CIMTUser user = manager.UserCreate();
res = manager.UserRequest(login, user);
string group = user.Group();

user.Group("prop\\phase-2");
res = manager.UserUpdate(user);

res = manager.DealerBalance(
    login, 500.00,
    (uint)CIMTDeal.EnDealAction.DEAL_BALANCE,
    $"PSP:{pspTxnId}",           // reference for reconciliation
    out ulong dealTicket);

CIMTAccount acc = manager.UserCreateAccount();
res = manager.UserAccountRequest(login, acc);
double equity = acc.Equity();

CIMTPositionArray positions = manager.PositionCreateArray();
res = manager.PositionRequest(login, positions);

CIMTDealArray deals = manager.DealCreateArray();
res = manager.DealRequest(login, fromUnix, toUnix, deals);

A platform API is a privileged interface.

Automation against a live trading server is only an improvement if the controls around it are stronger than the manual process it replaces.

A manager connection can move money and change account permissions. Treating it like an ordinary application credential is the most common mistake we are asked to correct.

Where a workflow needs judgement — a disputed payout, an unusual withdrawal, a suspected rule breach — the integration raises it for human approval instead of acting.