A MetaApi alternative for MT4 and MT5.

Why developers look for a MetaApi alternative

MetaApi is a cloud API for MetaTrader. Its home page offers one API for both MT4 and MT5 and says it works with any MetaTrader broker. So the reason to look elsewhere is more often fit than function. You may want a different way of working, or a different kind of bill.

Reasons to compare can include:

• plain HTTPS calls that return JSON, with no SDK and no socket to keep alive;
• a flat monthly price per account, rather than a bill tied to the hours an account is deployed;
• a trade copier or a signal copier on the same accounts.

The TPcopier API covers those three points. However, it does less than MetaApi in some areas. We list them near the end, so you can decide with the full picture.

MetaApi and TPcopier, point by point

This table is the quickest way to judge a MetaApi alternative. Each MetaApi cell comes from MetaApi's own pages, linked under the table. Where we could not read a fact, we say so.

Point	MetaApi (its own pages)	TPcopier
Platforms	MT4 and MT5, any MetaTrader broker	MT4 and MT5, each with its own broker and server list
How you call it	REST and a websocket API; its docs point to REST for monitoring and websocket for trading	REST only, JSON over HTTPS, plus webhooks and a price stream
SDKs	Official SDKs for browser JavaScript, Node.js, Python and Java	None; an OpenAPI file describes every endpoint
Starting an account	You deploy it; billing runs while it is deployed	It starts once added; there is no deploy step
Regions	Data centres in several regions; your URL must match the account's region	No region to pick; TPcopier places the account
Rate limits	CPU credits: most calls cost 50, a trade 10; 5,000 credits per account each 10 seconds	120 requests a minute per key
Market depth	Level-2 depth for selected symbols	Not offered
Copy trading	CopyFactory, a separate API	The MT4/5 cloud copier, with the same key
Price	A paid service; the figures are in its pricing section, which we could not read	Requests are free; accounts are paid per month (see below)

Sources, checked on 29 October 2026: MetaApi home, API docs, API FAQ, rate limiting, SDKs and CopyFactory. MetaApi may have changed them since.

An MT5 REST API with one key

Every call is HTTPS, with your key in the Authorization header or in X-API-Key. There is no socket to hold open and no terminal state to keep in step inside your process. Instead, each read asks the account's own terminal, which runs in our cloud. You can read:

• the account: balance, equity, margin, free margin and margin level;
• open positions and pending orders;
• deals from the last N days, each with its profit, commission, swap, magic number and comment;
• the broker's symbols, one symbol's specification, its price and its candles.

# read account A's open positions
GET  .../accounts/A/positions
Authorization: Bearer tpc_...

# buy 0.10 lots of EURUSD with a stop loss, in MetaApi's own field names
POST .../accounts/A/trade
{"actionType":"ORDER_TYPE_BUY","symbol":"EURUSD","volume":0.1,"stopLoss":1.0750}

It is an MT4 REST API in the same way: the same endpoints serve both platforms. Symbols are matched per account, so XAUUSD reaches XAUUSDc on a cent account, and the answer names the symbol it used. Full paths are in the API reference.

A trade answer carries MetaTrader's own result code, such as 10009 for a filled request. MetaQuotes lists every code in its trade server return codes. Each answer also has a timing block in milliseconds: our checks, the trip to the cloud server, the terminal's queue and the broker's own part. So a slow broker shows up as a slow broker.

Adding an account is one POST with the account number, password, server and platform. The broker and server lists our app shows are an endpoint too, so your own sign-up form can offer them.

Moving MetaApi code over

Moving code is often the real cost of any MetaApi alternative, so we kept the names. The trade endpoint accepts MetaApi's action names, such as ORDER_TYPE_BUY_LIMIT, POSITION_MODIFY and ORDER_CANCEL. It also takes MetaApi's camelCase fields: actionType, openPrice, stopLoss, takeProfit, positionId and orderId. As a result, most trade calls move over with a new address and a new key. The reads map one to one:

MetaApi call	TPcopier endpoint
get_account_information	GET .../accounts/{aid}/account-information
get_positions, get_orders	GET .../positions, GET .../orders
get_deals_by_time_range	GET .../history?days=N
get_historical_candles	GET .../symbols/{symbol}/candles
deploy, undeploy	POST .../action with start or stop

The full map sits in the MT4/MT5 trading guide. What does not move over is the SDK's streaming listeners; webhooks take their place.

Before an order opens, your own limits for that account apply: the largest lot, no order without a stop loss, and the most orders a day. Closing and changing a position never hit these limits, because they only lower risk. Each API trade goes into a log with its answer.

Events: webhooks instead of a socket

MetaApi's FAQ asks developers to use an SDK for its streaming API. TPcopier takes the other road and calls your server. For a MetaApi alternative, that is the biggest change in how your code listens. You give an address and a secret, and a signed POST arrives when something happens:

• position.opened, position.updated and position.closed, from any source;
• account.connected and account.disconnected;
• copy, when the copier copied a trade or did not, with both tickets and its latency;
• protection.tripped, plus account, slot and wallet events;
• signal, for each message a binary channel sends, with the asset, direction, expiry and reason.

Each request is signed with HMAC-SHA256 over the timestamp and the raw body. Events arrive within about five seconds, as our cloud server reports them, and a failed delivery is tried twice more. For prices, one request streams up to 20 symbols as Server-Sent Events, with five streams per workspace. Read the webhooks guide.

Live trades on the app's dashboard: each trade with its direction and result, beside the month's calendar (example workspace). The signal webhook carries the asset, direction, expiry and reason for each message.

CopyFactory and the cloud trade copier

MetaApi sells copy trading as CopyFactory, its own API. Its page says MT5 netting accounts are not supported in the current version, and it states a median copy latency of about 5 ms. In TPcopier, the copier is part of the same API, used with the same key.

A sender and its receivers form a pipeline. Each receiver has a lot rule (multiplier, fixed lot, risk percent or balance ratio), a symbol map, filters, trading hours and a daily loss limit. Equity protection can send you a notice, pause copying, or close all positions. Every copy is listed with the sender's ticket and the receiver's ticket.

Our own speed: TPcopier's side took a median 7 ms, from the moment the copier sees a new trade on the sender until the receiver's order goes out. We measured it on live copies on 4 October 2026. Broker execution added about 140 ms. These come from a different measurement than MetaApi's figure, so read them side by side, not as a race. More on the MT4/MT5 cloud trade copier page and in the copier guide.

The same key also runs the signal copier. Link a Telegram, WhatsApp or Discord channel, or a TradingView feed, to a cloud MT4/MT5 account. Then read each signal and the order it turned into.

The TradingView page: the webhook URL to paste into TradingView, the MT5 account linked to the feed, and the alert message builder (example workspace). The API makes and links feeds like this one.

MetaApi pricing compared with ours

Price is where a MetaApi alternative differs most, so here are both models. MetaApi's docs call it a paid service. Its FAQ says an account costs money only while its API server is deployed, that each start bills 6 hours, and that you can stop the server at any time. Its prices are in the pricing section of its home page. We could not read the figures there on 29 October 2026, so we do not quote them. Please check them on its site.

TPcopier does not bill requests. You fund a wallet in USDT (TRC20) from the app. An account your code trades alone takes one slot of the MT4/5 copier, at $6 a month per account. Each slot runs a month from the moment you pay and renews from the wallet a day before its own end. In a copier, the sender comes free with its receivers.

The limit is 120 requests a minute for each key. A workspace can hold up to 20 keys, full or read-only. Payments are final, which is why a demo test comes first. Every price is on the pricing page.

When MetaApi is the better fit

No MetaApi alternative is right for every project. MetaApi is the better choice when you need:

• official SDKs in JavaScript, Python or Java (we have none);
• Level-2 market depth, which MetaApi lists for selected symbols;
• its other products: MetaStats for statistics, the MT Manager API or its risk management API;
• a region chosen for each account;
• access at once, since TPcopier turns the API on per workspace when you ask in the app.

On the other hand, TPcopier suits you if you want plain REST, a flat monthly price per account, and a trade copier or signal copier on the same accounts. It also reaches binary broker accounts: one link opens a cloud sign-in window on your own site, where your user signs in to the broker. In any case, neither API makes a strategy profitable, so start on demo.

New to the API? Start at the developer docs. Copying Telegram signals instead? Read about our Telegram signal copier for MT5.