The XFIV developer hub is where brokers and their engineering teams start building on MT5. XFIV Connect gives you a REST API described in OpenAPI, webhooks for account and trading events, a sandbox with sample data and an MCP layer for AI assistants. This page explains what is available and where to go next.
Most MT5 brokers end up with a patchwork of scripts, plugins and point-to-point integrations. Each one talks to the MT5 server in its own way, with its own credentials and its own failure modes. XFIV Connect replaces that patchwork with one documented layer that sits between your MT5 server and the systems around it.
Your CRM, client portal, payment flows, reporting tools and AI assistants all call the same API. Access is controlled with scoped keys, every call is written to an audit log. XFIV Portal, XFIV Trade, XFIV Copy and XFIV BrokerOS use the same layer, so anything they can do, your own systems can be built to do as well.
Documentation, sandbox access and keys are provided to brokers during onboarding, and compatibility with your MT5 build is confirmed before anything touches production.
Every capability of XFIV Connect is described in an OpenAPI specification. Read it in the browser, import it into your API client, or generate a client library in the language your team already uses.
Subscribe to account, trading and funding events and receive them as signed webhook payloads. Your systems verify the signature, process the event and move on, without hammering the MT5 server for changes.
The sandbox mirrors the production API with sample accounts and data. Build, break and fix your integration there, then switch keys when you are ready to go live.
The reference documentation groups operations by area. The table below is a summary of what each area is for, not a list of endpoints.
| Area | What you can do | Typical use |
|---|---|---|
| Accounts | Create MT5 accounts and read account details, balances and equity | Client onboarding from a portal or CRM |
| Trading data | Read open positions, orders and trading history | Client dashboards, statements and reporting |
| Funding | Read and record deposit and withdrawal activity | Back-office reconciliation and approvals |
| Webhooks | Subscribe to events and inspect delivery history | Near real-time CRM updates and notifications |
| MCP | Expose scoped, read-only account data to approved AI assistants | Client-facing AI assistants and agents |
| Administration | Manage API keys, scopes and audit logs | Security reviews and access control |
XFIV Connect is the core every product runs on. It links your MT5 server to the portal, terminal and copy engine through one documented API, with webhooks for near real-time events, a sandbox for testing, and an MCP layer so approved AI assistants can read data safely.
We review your MT5 setup, confirm build compatibility and agree on what you want to integrate.
You receive documentation and sandbox keys scoped to the areas you need.
Integrate against sample data, subscribe to webhooks and check the audit log for every call.
Decide which keys and AI clients can read what in production, following least-privilege access.
Switch to production keys, start with a limited group of accounts and monitor the logs.
A few habits make MT5 integrations easier to run over time. The documentation covers each in detail.
Give your CRM, portal and reporting tool separate keys so you can scope and revoke each one on its own.
Check the signature on each payload before you act on it, and treat repeated deliveries as normal.
Rate limits protect your MT5 server. Back off and retry when a limit is reached instead of looping.
When something looks wrong, the audit log shows which key called what and when.
How XFIV Connect lets approved AI assistants read client data with broker-set scopes and full logging.
Read moreThe product page for the MT5 integration API, webhooks and MCP layer.
Read moreHosting, encryption, access control and how we handle AI and MCP access.
Read moreA glossary entry on the MT5 Manager API and how an integration layer relates to it.
Read moreDocumentation and the OpenAPI specification are shared with brokers during onboarding, together with sandbox access. Book a demo to start that process.
XFIV Connect handles the connection to your MT5 server for you. Your systems call XFIV Connect instead of working with the MT5 server directly. Compatibility with your MT5 build is confirmed during onboarding.
Yes. The sandbox mirrors the production API with sample accounts and data, and uses separate keys.
Yes, through the MCP layer in XFIV Connect. Access is read-only by default, scopes are set by the broker and every request is logged. AI assistants do not place trades.
The backend is written in Go. You can call the REST API from any language and generate clients from the OpenAPI spec.
Book a technical call. We will confirm compatibility with your MT5 build and set you up with documentation and sandbox keys.
Last reviewed 2026-10-29
