Forex CRM and the MT4/MT5 Manager API: What You Are Actually Paying For
The line item reads “Manager API integration”, and the price is large. What does it buy? This guide breaks the connection into the pieces a buyer should see in a quote, so you can compare vendors and avoid paying for work you will not get.
What the connection does
The Manager API lets your CRM administer accounts on the trading server: create accounts, change groups, apply balance operations and read account data for reports. Our Manager API for CRM page explains the idea.
Insist on a workflow list
A quote should name each workflow it covers, for example account creation, group changes, deposits and withdrawals as balance operations, and report feeds. “Full integration” is not a scope. Any workflow not named is not included.
Check access and permissions
On a grey label, deeper management access may be limited or optional. Ask your provider in writing what access your setup includes before you pay a CRM vendor to build against it.
What testing and support should include
- A test environment and a written test plan.
- Handling of failed and repeated calls.
- A warranty period after go-live.
- Monthly support, with response times.
Ask for the price of future changes now.
Red flags in the quote
Beware a single price with no breakdown, no mention of failure handling, no test environment and no statement of who holds the credentials. For the wider buying checklist see the Forex CRM buyer’s guide.
Hold back part of the payment
A sensible commercial structure ties part of the integration fee to acceptance: the workflows pass the written tests on a test environment, then in production for a short trial period.
If the vendor refuses any link between payment and acceptance, treat that as a risk and ask for a warranty period instead. Either way, define what “working” means before work begins.
A workflow list to attach to the quote
The quote should name each workflow the connection must perform. Attach a table like this one and ask the vendor to confirm it.
| Workflow | Included | Test evidence | Notes |
|---|---|---|---|
| Create trading account after approval | |||
| Credit deposit | |||
| Debit withdrawal | |||
| Change group | |||
| Block or unblock account | |||
| Read balances and positions for reports |
A workflow that is not on the list is not in the price.
A worked example of a price that grew
A buyer is quoted a fixed sum for "Manager API integration". During implementation, the vendor explains that withdrawals, group changes and reporting were not part of the original scope. Each is quoted separately. The final cost is nearly double the first.
If the buyer had attached the workflow list, each row would have been agreed in advance. The vendor might still have charged for extra rows, but the buyer would have known the full price before signing.
Access and permissions
Ask what permissions the integration will use. A read-only connection is simpler and safer, but it cannot credit balances. A write connection is powerful and needs careful limits, logging and credentials. Ask the vendor to explain how keys are stored and rotated and what happens if a key is exposed.
Treat the integration as a privileged connection, because that is what it is.
Testing, support and payment
The quote should include a test plan with expected results, support for the connection after go-live and a warranty period for defects. Pay in stages: part on signing, part on delivery to a test environment and the final part after your tests pass.
See our security guide for controls to demand.
Why integration quotes vary so much
Integration prices differ because vendors assume different scopes, different levels of testing and different amounts of support. One quote may include a full test plan and a warranty; another may include only the technical connection. A cheaper quote with fewer deliverables is not cheaper.
Compare quotes by listing the deliverables and mapping each to a row in the workflow table. Differences become visible, and you can ask each vendor to match the strongest offer.
Warranty and defects
Ask how long the vendor will fix defects at no charge after delivery, and what counts as a defect. A warranty of a few months is common. Clarify the difference between a defect, which the vendor fixes, and a change, which you pay for.
Write the definition into the contract. It prevents arguments about whether a problem is a bug or a new request.
Ongoing costs
After delivery, an integration needs monitoring, updates when either system changes and occasional fixes. Ask what the vendor charges for these and whether there is a maintenance plan. Add the cost to your budget, because an unmaintained integration will eventually break at a bad moment.
Asking for a technical walkthrough
Before you buy, ask the vendor to walk you or your technical adviser through how the integration works: which interface it uses, how requests are authenticated, how errors are handled, how often data is synchronised and what happens when the platform is unavailable. Ask for a diagram.
A vendor that can explain its own integration clearly is more likely to build one that works. A vendor that cannot is telling you something about the project ahead.
Versions and updates
Platforms and CRMs both change. Ask how the vendor tracks changes to the platform interface, how it tests updates and how quickly it fixes problems. Ask whether you will be told before an update and whether you can test it first.
An integration that is not maintained will eventually fail. The cost of maintenance should be in your budget.
Asking for a sample of the documentation
Ask the vendor for a sample of the integration documentation: workflow descriptions, configuration details, error handling and operating procedures. Good documentation reduces dependence on the vendor and speeds up troubleshooting.
If the vendor has none, add the cost of creating it to the quote, or ask for it as a deliverable.
Frequently asked questions
Is the Manager API included in a grey label?
It depends on the setup. Ask whether it is included, optional or unavailable.
What should an integration quote include?
The workflows, the test plan, access permissions, support and a warranty.
How do I avoid scope creep?
Attach a workflow list to the contract and require changes to be agreed in writing.
When should I pay the final instalment?
After your acceptance tests pass.