Migrating from MetaApi to fxapis

This guide is for teams with an MT5 integration on MetaApi who are evaluating or planning a move to fxapis. It maps MetaApi's concepts to ours, lists equivalent calls, and is explicit about what fxapis does not have yet, so you can decide with the full picture.

The MetaApi details below come from its public documentation, read on 30 September 2026; see Sources. MetaApi changes over time — check its current docs for anything your decision depends on.

The short versionCopy Anchor Link

If your product depends on streaming updates, MT4, market data or CopyFactory's risk features, fxapis does not replace them today. If it places orders on MT5 accounts — one at a time or across many — and needs a recorded result for every order, with an unclear one confirmed with the broker rather than guessed, read on.

ConceptsCopy Anchor Link

Provisioning and deploy → connect and modesCopy Anchor Link

In MetaApi you create an account through the provisioning API (POST /users/current/accounts with name, server, login, password, platform, magic and options such as type, region and reliability), then deploy it (POST …/deploy), which starts an API server and a trading terminal for it, and undeploy it to stop them.

In fxapis you connect an account with POST /v1/accounts — login, server, password, and a mode. The mode replaces manual deploy/undeploy:

Coming online takes about ten seconds in our tests. MetaApi's waitConnected() and waitSynchronized() correspond to polling GET /v1/accounts/{id}/status until state is ready. POST /v1/accounts/prepare brings up to 200 accounts online in one call.

There is no magic field: fxapis tags each order's MT5 comment so it can match the broker's record to your order, and gives you clientOrderId for your own reference.

RPC and streaming connections → REST and pollingCopy Anchor Link

MetaApi offers an RPC connection (account.getRPCConnection()), which its docs recommend for monitoring apps and simple trading apps, and a streaming connection (account.getStreamingConnection()), recommended for trade copiers and automated strategies, which keeps a synchronized local terminal state and calls your listeners on every change.

fxapis has one interface: REST. What you would read from a streaming connection's terminal state you read with requests:

• Positions: GET /v1/accounts/{id}/positions — a snapshot refreshed about every 15 seconds while the account is online, with observedAt on each row. POST /v1/accounts/{id}/reconcile refreshes it immediately.
• Deals: GET /v1/accounts/{id}/deals, including deals not caused by your orders (stop-outs, swaps, deposits, manual trades).
• Order outcomes: returned by the order call itself, and by GET /v1/orders/{id}.

There are no event webhooks yet. Code that reacts to onPositionUpdated or onDealAdded becomes a polling loop; the copier guide shows one.

TradesCopy Anchor Link

MetaApi places trades through one endpoint, POST …/trade, with an actionType. fxapis has one endpoint per intent, and every order that opens or closes exposure takes an Idempotency-Key:

• A retry with the same key returns the first answer instead of placing a second order, for 24 hours.
• Three failures are distinguished: SEND_FAILED (never reached the broker — safe to retry), ORDER_REJECTED (the broker refused, with its retcode), and ORDER_UNRESOLVED (the answer was lost — do not resend; the order is confirmed against the broker's records and moves to what actually happened).
• Volumes and prices are strings: "0.01", never 0.01.

See Idempotent MT5 orders and Trading.

CopyFactory → multi-account orders and a copierCopy Anchor Link

CopyFactory is a complete copy-trading product: strategies and subscribers, per-subscription copy ratios, symbol mapping, risk filters (drawdown, equity curve, leverage), stop-outs and signal filtering, with very low internal copying latency per its docs.

fxapis provides the execution building block — multi-account orders, one trade sent to up to 500 accounts together on Enterprise (accounts per multi-account order: Starter 10, Scale 100, Enterprise 500), with per-account volumes, barrier policies and a dispatch spread of about 30 ms across 100 accounts in our benchmark against an instant broker — every multi-account order reports its own — and you build the copying logic. The trade copier guide is a working starting point. Risk filters, stop-outs, symbol mapping and subscriber management are yours to implement.

Equivalent callsCopy Anchor Link

No equivalent yetCopy Anchor Link

Be sure none of these is load-bearing for you:

• Streaming. No WebSocket connection, synchronization listeners or webhooks. Poll.
• MetaTrader 4. fxapis connects MT5 accounts only.
• CopyFactory features. No strategy/subscriber model, risk filters, stop-outs or symbol mapping.
• Market data. No quotes, ticks or candles.
• Demo account creation. fxapis does not open accounts at brokers; you connect existing ones.
• Account balance and equity fields. Derive them from deals and positions (see prop-firm monitoring).
• Official SDKs. Any HTTP client works; the language guides have complete programs for seven languages.

A migration planCopy Anchor Link

SourcesCopy Anchor Link

MetaApi documentation, read on 30 September 2026:

• MetaApi — Provisioning API overview
• Create account, Deploy account, Undeploy account
• MetaApi — Client API overview (REST and WebSocket, MT4 and MT5, SDKs)
• Execute trade, Read positions, Read deals by time range
• JavaScript SDK — RPC API and Streaming API
• CopyFactory overview

fxapis facts on this page are from our own API reference and measurements.