Ask three MetaTrader integrators which API your CRM should use and you will get three answers. That is not evasion — MetaQuotes ships several distinct interfaces, they solve different problems, and the one you need depends on what you are actually building.
This guide separates the MT5 Manager API vs Web API question properly, adds the Gateway API for completeness, and gives you a decision rule you can apply to your own project.
The Three Interfaces at a Glance
| Manager API | Web API | Gateway API | |
|---|---|---|---|
| Purpose | Programmable admin terminal | Web/service integration | External venue connectivity |
| Typical language | C++ / .NET wrapper | Any (HTTP/JSON) | C++ |
| Runs | Beside the server | Over the network | As a server component |
| Creates accounts | Yes | Yes | No |
| Balance operations | Yes | Yes | No |
| Closes positions | Yes | Limited | Via routing |
| Real-time event stream | Yes | Polling or callback | Yes |
| Feeds prices in | No | No | Yes |
Manager API: Your Admin Terminal, Programmable
The Manager API is the same capability set your dealing desk has in the Manager terminal, exposed as a library. Account creation, group assignment, leverage changes, balance and credit operations, position management, symbol configuration, and a real-time stream of trading events are all available without a human logged into a terminal.
It is the right choice when you need:
- Real-time equity monitoring. Prop firms enforcing drawdown rules cannot poll every few seconds and hope. The Manager API pushes trade and equity events as they happen — the difference between stopping a breach and discovering one. This is the backbone of any serious prop fund broker CRM.
- Automated position closure. Liquidating a breached account or a disqualified challenge trader requires server-side authority the Web API does not fully grant.
- Bulk configuration. Moving 4,000 accounts between groups after a spread change is a loop, not a week of clicking.
- MAM and allocation engines. Splitting a master fill across sub-accounts at execution speed needs this level of access.
The cost is operational. The Manager API is a native library that expects to run close to the server, it is version-locked to your MT5 build, and a server upgrade can require you to rebuild your integration. Budget for that maintenance rather than being surprised by it.
Web API: The Integration Layer
The Web API is a network-facing interface designed for exactly the job most brokers need first: letting a website, a CRM, or a third-party service talk to the trading server over HTTP. Register a client from your web form, open a live account, credit a verified deposit, pull account state for the client cabinet, fetch trade history for a report.
It is the right choice when you need:
- Client registration and account opening from your trader cabinet
- Deposit and withdrawal processing triggered by your payment gateway
- Account state and history for dashboards and statements
- Integration from a stack that is not C++ — Node, Python, PHP, Go
It is also far kinder to operate. No native library on the server host, no rebuild on every platform update, and a deployment model your existing web team already understands.
Gateway API: A Different Problem Entirely
The Gateway API is not a back-office interface at all. It exists to connect MT5 to external execution venues and data sources — building a custom bridge to a liquidity provider, injecting a proprietary price feed, or routing orders to an exchange MT5 does not natively support.
If your question is “how does my CRM create an account”, the Gateway API is not the answer. If your question is “how do I route A-book flow to a specific LP”, it is. Most brokers consume this through a commercial liquidity bridge rather than writing one.
The Decision Rule
In practice, the MT5 Manager API vs Web API decision resolves like this:
- Start with Web API. It covers registration, funding, and reporting — which is 80% of what a broker CRM does — with a fraction of the operational burden.
- Add Manager API when you need real-time authority. Prop challenge enforcement, MAM allocation, automated risk liquidation, and bulk administration all require it.
- Use Gateway API only for connectivity. And usually via a vendor bridge.
Most mature brokers run both Web API and Manager API side by side, which is the correct architecture rather than a compromise: the Web API serves everything client-facing, and a hardened Manager API service handles risk and administration.
Three Things to Settle Before You Build
- Access rights. Manager API access is granted per manager login with a specific permission mask. Build against a dedicated, tightly scoped login, never a full-rights administrative account.
- IP allowlisting. Both interfaces should be reachable only from your application hosts. An exposed Manager API endpoint is a balance-operation endpoint.
- Idempotency. A deposit retried after a network timeout must not credit twice. Key every balance operation on your own transaction reference and check before writing.
If you are still deciding between platforms, our comparison of MT4 and MT5 for brokers is worth reading first — MT4’s API surface is materially narrower, and that constrains what you can automate later.
The ForexPlatforms.Pro broker CRM ships with both sides of the MT5 Manager API vs Web API question built and maintained — Web API for onboarding, funding, and cabinet data, and a supervised MT5 Manager API service for real-time risk, allocation, and bulk administration. Server build upgrades are handled on our side.
Related Guides
- MT5 Web Manager — a browser back office for MT5, with history import
- How to Import Trade History into MT5 — orders plus IN/OUT deals, and what breaks imports
Frequently Asked Questions
Q: What is the difference between the MT5 Manager API and the Web API?
A: The Manager API is your admin terminal exposed as a native library, with real-time trade events and full server-side authority. The Web API is a network-facing HTTP interface for web and service integration — registration, funding, account state. Most brokers need both.
Q: Which API does a forex CRM need?
A: Start with the Web API. It covers client registration, account opening, deposits, withdrawals, and reporting, which is most of what a CRM does, with far less operational overhead. Add the Manager API when you need real-time equity monitoring, automated position closure, MAM allocation, or bulk administration.
Q: What is the MT5 Gateway API used for?
A: Connecting MT5 to external execution venues and data sources — custom liquidity provider bridges, proprietary price feeds, or exchange routing. It is a connectivity interface, not a back-office one, and most brokers consume it through a commercial liquidity bridge rather than building one.
Q: Does the Manager API break when the MT5 server is upgraded?
A: It can. The Manager API is a native library version-locked to your server build, so a platform upgrade may require rebuilding the integration. Budget for that maintenance, or use a provider who handles build compatibility on their side.