MT5 Manager API vs Web API vs Server API

What is the MT5 Manager API?

The MT5 Manager API is the interface MetaQuotes provides for writing your own administration and management software for a MetaTrader 5 server. Anything a back-office employee does in the MT5 Manager terminal — opening accounts, moving them between groups, posting deposits, watching positions, handling dealer requests — can in principle be done from a program built on it.

It is delivered to licence holders as part of MetaQuotes’ developer packages rather than as a public download, and the documentation sits on MetaQuotes’ support site behind a login. In the packages we have worked with, it is a native library for Windows with headers for C++ and wrappers for .NET; check the current package for your server build, because details change.

How do the Manager API, Web API and Server API compare?

The quickest way to tell them apart is to ask where the code runs and what happens if it fails. Manager API and Web API programs run outside the server and connect to it; a Server API plugin runs inside it, on every relevant event.

Where do the Gateway API and Report API fit?

They complete the set but answer different questions. The Gateway API connects MT5 to other trading systems and data feeds, which is how liquidity providers and exchanges are attached; we cover it in the MT5 Gateway API guide. The Report API extends the reports the trade server produces, which matters for regulatory and management reporting.

Neither is a substitute for the Manager or Web API. A CRM that needs to open accounts will never use the Gateway API, and a liquidity connection will never be built on the Web API.

What do brokers automate with the Manager API?

Brokers use the Manager API mostly for work their own staff would otherwise do by hand in the Manager terminal, at scale or around the clock. Common examples from projects we have seen:

• Account administration — creating accounts in bulk, moving clients between groups, changing leverage after an appropriateness review.
• Balance operations — posting deposits, withdrawals, credit and corrections from an approved payments queue.
• Dealing and risk tools — custom screens for net exposure per symbol, large-position alerts and client profitability.
• Introducing broker reporting — pulling deals for commission calculations at the end of each day.
• Compliance checks — flagging accounts that trade outside expected patterns or hold positions over weekends.
• Housekeeping — archiving inactive accounts, cleaning up test groups, checking symbol settings against a master list.

Worked example: from KYC approval to the first trade

Say a broker approves a new client in its CRM at 10:00 on a Tuesday. This is how the work splits between interfaces in a typical integration; in a web-based CRM, as in ours, the manager-level calls usually go through the Web API.

1. KYC approvedThe compliance officer approves the documents in the CRM. The CRM checks the client’s country and assigns the right MT5 group.
2. Account createdThe CRM calls the server as a manager to create the account with name, group, leverage and a generated password, then shows the login in the client area.
3. Deposit creditedThe payment provider confirms a card deposit. After the CRM’s own checks, a balance operation is posted to the account with the payment reference in the comment.
4. Client tradesThe client logs in to the WebTrader or app and opens a position. A Server API plugin, if the broker has one, can apply custom rules at this point.
5. ReportingOvernight, a reporting job reads the day’s deals for IB commissions and the risk team’s dashboard.

When is the Web API a better choice than the Manager API?

The Web API is usually the better choice when the consumer is a web service running on Linux, in the cloud or in a language other than C++ or .NET. It speaks HTTPS and JSON, so a CRM written in PHP, Node.js, Go or Python can use it without a native library. That is why most CRMs and portals, ours included, are built on it.

The Manager API earns its place when you are building a desktop tool for dealers, need the full set of manager functions in a native application, or want to react to server events without polling. A risk monitor that has to show exposure changing in real time is a typical case. Our MetaTrader 5 Web API guide explains the Web API’s limits in more detail.

What is an MT5 Server API plugin, and when do you need one?

A Server API plugin is code that runs inside the MetaTrader 5 trade or history server and is called as events happen — a trade request, a deal, a change to an account. You need one when a rule has to be enforced on every operation, before the result is final, and cannot wait for an outside program to notice.

Examples include custom margin or exposure checks, bonus rules that depend on trading volume, copy-trading logic that must react immediately, or extra data written to deals for reporting. The power is also the risk: a slow or faulty plugin slows or stops the server for everyone. We advise clients to keep plugins small, test them on a separate server with realistic load, and keep anything that can run outside the server outside it.

Which MT5 API should you use for each broker job?

Match the interface to the job, not to whichever one your developer already knows. The table reflects how we would build each item today.

Who can get MT5 Manager API access?

Access comes from the owner of the MT5 server, because every manager account is created on that server. With your own MT5 licence you decide who gets which manager and which developer packages you use. In a white label, the licence holder decides, and the manager you receive is normally limited to your groups. In an MT5 grey label you generally work through the provider’s CRM and front ends rather than holding raw manager credentials.

This is one of the questions to settle before you sign. If your plans include a custom dealing tool or an in-house CRM, ask your provider in writing what level of API access you will get and on what terms. We are independent and not affiliated with MetaQuotes; for licence questions about API packages themselves, MetaQuotes or your server provider is the right contact. If you are applying for your own MT5 licence, we handle the MetaQuotes requirements and application for clients as a consulting service, for a fee.

Not sure what to ask for? Send us a WhatsApp message describing your setup and we will suggest the wording.

What about third-party “MT5 API” services?

Many products sold as an “MT5 API” are not MetaQuotes’ broker APIs at all. Some connect to individual trading accounts by running terminals on the vendor’s cloud; others wrap MetaQuotes’ Python package, which talks to a desktop terminal on the same machine. These suit traders, signal services and analytics, and they work with any broker’s accounts.

Others are hosted wrappers around the Manager or Web API, giving a REST interface on top of a manager connection. They can save development time, but your manager credentials then sit with a third party, and you depend on their uptime and their update cycle when MetaQuotes releases a new build. Ask where the service is hosted, who can see the credentials and what happens to your integration if the vendor stops trading.

How do you keep a manager-level integration safe?

Treat every manager account used by software as a privileged system account, because that is what it is. The rules we apply on our own integrations:

• One manager per integration, with only the rights and groups that integration needs.
• Balance operations only from an approved queue, never directly from a client-facing request.
• Credentials in a secrets store, rotated when staff or vendors change.
• Connection allowed only from known servers.
• Every write logged with the business reason and reconciled daily.
• No automatic retry of money movements or trades after a timeout; check the server state first.

What are the common mistakes in MT5 Manager API projects?

The common mistakes are architectural, and most of them are made in the first week. They are cheap to avoid and expensive to fix once clients depend on the system.

• One manager for everything. The CRM, the reporting job and the dealer tool share a login with full rights, so nobody can tell which system made a change and none of them can be revoked separately.
• Polling account by account. A portal that asks for each client’s positions in turn works with 50 accounts and slows the server at 5,000. Use batch requests and cache what does not change.
• Business logic in a plugin. A copy trading or bonus rule written as a Server API plugin because it felt “closer to the server”, when it could run safely outside.
• Ignoring server time. Deals stored in the CRM in server time and compared with payment records in UTC, so daily reconciliations are off by two or three hours.
• Retrying money movements. A deposit call times out, the code tries again, and the client is credited twice. Check the account history before any retry.
• No plan for MT5 updates. MetaQuotes releases new builds regularly. Keep a test server on the next build and run your integration against it before the live server is updated.

Does a prop firm or copy-trading project change the choice?

Yes, a little. Prop trading technology leans heavily on fast, rule-based account actions — closing an evaluation account the moment a drawdown limit is breached, for example. Some firms do that from outside through the Web or Manager API with frequent checks; others prefer a plugin so the rule is enforced inside the server. The trade-off is reaction time against the risk of running custom code on the server.

Copy trading and PAMM sit in a similar place. The copying itself can run outside the server, but the allocation of volume and fees has to be exact, so the interface you choose must give you reliable deal data and a way to reconcile. Liquidity is separate again: if the project also needs new providers, see liquidity provider integration.

How does FXUP work with the MT5 APIs?

Our branded WebTrader, mobile apps and own broker CRM connect to MT5 through a Go back end that uses the Web API. We also work with partner CRMs and propose whichever fits the project; either way, we check which interface and manager rights the CRM needs before anything goes live. For clients with their own server we also scope dealer tools, reporting jobs and the occasional plugin, and we will tell you when an existing MT5 feature or a simpler interface would do the job instead.

If you are comparing quotes for an API project, send us the specification on WhatsApp; we can tell you which interface each item needs and where the hidden work is. Our custom integrations page lists the kinds of projects we take on.

Questions buyers ask

Not covered here? Ask us on WhatsApp, message @FXUPCK on Telegram or write to [email protected].