Main clusters and core pages.
AlgoWay MT5 Copier EA is used when MetaTrader 5 is the signal source. It watches trades opened on your source MT5 account and sends them to an AlgoWay webhook. AlgoWay then routes those trade events to the selected destination platform, such as TradeLocker, DXtrade, cTrader, Match-Trader, Tradovate, ProjectX, Binance, OKX, Bybit, MEXC, BitMEX, or another supported execution route.
This page replaces the older per-platform MT5 copier manuals. The current workflow uses one EA file:
Download AlgoWay-MT5-CopierBot.ex5
This guide is written for traders searching for MT5 copier EA, MetaTrader 5 trade copier, MT5 to TradeLocker copier, MT5 to DXtrade copier, MT5 to cTrader copier, MT5 copy trading bot, MetaTrader webhook copier, and AlgoWay trade copier. This is not a TradingView alert setup page. TradingView is not the source in this workflow. The source is your MetaTrader 5 terminal.
The normal route is:
Source MetaTrader 5 account → AlgoWay MT5 Copier EA → AlgoWay webhook → destination platform
For MT5 to MT5 copying, the route is different and has a separate section below. In that case, the destination MT5 account must be connected through the AlgoWayWS-MT5 WebSocket EA, and Clone Mode is used to forward the copied JSON to the destination MT5 webhook.
Last updated: 2026-05-13 • Product: AlgoWay MT5 CopierBot • Source platform: MetaTrader 5
To copy trades from MetaTrader 5 through AlgoWay:
https://algoway.co to Allow WebRequest for listed URL.The MT5 Copier EA is a source-side bridge. It is installed on the MetaTrader 5 account where trades are opened. When a new position appears, changes, or closes, the EA sends the relevant trade event to AlgoWay. AlgoWay then translates that event into the destination platform format.
This makes the EA useful for several copy-trading and cross-platform automation workflows:
The copier does not need a TradingView alert. It does not need Pine Script. It does not wait for a webhook from TradingView. The trade event starts from the MT5 source account itself.
AlgoWay has different automation routes, and confusing them is the most common setup mistake. This page is for MetaTrader 5 as the source. The correct source in the webhook form is MetaTrader.
| Workflow | Source | Tool installed | Use this guide? |
|---|---|---|---|
| TradingView alert to MT5 | TradingView | AlgoWayWS-MT5 EA on destination MT5 | No |
| MT5 trade copier to TradeLocker / DXtrade / cTrader | MetaTrader | AlgoWay-MT5-CopierBot.ex5 on source MT5 | Yes |
| MT5 to MT5 copy trading | MetaTrader source + MT5 WebSocket destination | CopierBot on source MT5 and AlgoWayWS-MT5 EA on destination MT5 | Partly; see MT5 to MT5 section |
If the wrong source is selected, the EA can show a red status such as Wrong Webhook or Invalid Webhook. That usually means the webhook UUID does not belong to a valid MetaTrader source route for this CopierBot workflow.
Open your AlgoWay dashboard and click the button to create a webhook. You can start with a 14-day trial webhook or create a main paid webhook. Functionally, the trial webhook works like the paid webhook during the trial period. After the trial expires, the same webhook can be activated with a subscription.
In the webhook form, use this logic:
For example, when copying MT5 trades to TradeLocker, the AlgoWay form must contain the TradeLocker URL, email, password, server and account ID. The EA itself only needs the AlgoWay webhook UUID or full URL. It does not need your TradeLocker password.
After the webhook is created, it appears in the dashboard. Copy the UUID or full webhook URL from the Webhook UUID column.
The current MT5 copier uses one Expert Advisor file:
AlgoWay-MT5-CopierBot.ex5
Download it here:
https://algoway.trade/downloads/MT5-Copier/AlgoWay-MT5-CopierBot.ex5
The old model with separate per-platform EA files is no longer the main setup. The current EA sends MT5 source events to AlgoWay, and AlgoWay handles destination routing according to the webhook configuration.
Install the .ex5 file into the MetaTrader 5 data folder of the terminal that will act as the source account. This is the MT5 account where trades are opened manually, by another EA, or by your own trading system.
Use the normal MT5 Expert Advisor installation process:
AlgoWay-MT5-CopierBot.ex5 into that folder.The chart symbol does not define the destination platform. The destination is defined by the AlgoWay webhook. The chart is the runtime place where the EA remains attached and running.
Before the EA can communicate with AlgoWay, MetaTrader 5 must allow automated trading and WebRequest access.
https://algoway.co
The new CopierBot communicates with AlgoWay. You do not need to add every destination platform URL inside MT5 for this current workflow. The required WebRequest domain is https://algoway.co.
After dragging the EA onto the chart, open the Inputs tab and configure the main fields.
| Input | What to enter | Purpose |
|---|---|---|
| AlgoWay Webhook (UUID or FULL URL) | Paste the copied webhook UUID or the full AlgoWay URL. | Identifies the AlgoWay route that will receive MT5 trade events. |
| SendPrice | true or false |
Sends the MT5 trade price with the copied event when enabled. |
| SendSLTPonOpen | true or false |
Sends Stop Loss and Take Profit values together with the open event when available. |
| Symbols Mapping | Examples such as NAS100:USTEC or XAUUSD:XAUUSD.m |
Maps MT5 source symbols to destination symbols when names are different. |
Symbol mapping is important because MetaTrader brokers and destination platforms often use different symbols for the same instrument. For example, the source MT5 account may use XAUUSD, while the destination may require a futures symbol, broker-specific symbol, exchange symbol, or a different contract code. The mapping tells the MT5 CopierBot how to translate the local MT5 symbol before AlgoWay sends the copied trade to the remote destination platform.
In the current MT5 CopierBot interface, symbol mapping is entered in the dedicated fields named Map 01, Map 02, Map 03 and so on. Each mapping field must use this exact format:
LOCAL_MT5_SYMBOL:REMOTE_DESTINATION_SYMBOL
The value before the colon is the symbol exactly as it appears in your local MetaTrader 5 source account. The value after the colon is the symbol required by the remote destination platform where the trade will be copied. Do not add spaces around the colon.
Examples:
XAUUSD:GC
EURUSD:6E
NAS100:NQ
BTCUSDm:BTCUSD
After filling the inputs, click OK. Keep the chart open and keep MT5 running.
When the configuration is correct, the chart panel should show that the EA is connected. It can display information such as the AlgoWay user, connection status and the destination platform.
A normal successful state looks like:
Status: Connected
Copy to: tradovate
If there is a problem, the status can appear in red. Common red statuses include:
https://algoway.co.When the status is red, do not open large test trades. First fix the webhook, subscription, source/platform selection or WebRequest setting.
After the EA shows connected status, test the copier with one small position from the source MT5 account.
The first test should prove the complete path:
MT5 source position opened → CopierBot sends event → AlgoWay receives event → destination platform receives copied order
If the source MT5 order opens but the destination does not copy it, do not guess. Check the logs in this order: MT5 Experts tab first, then AlgoWay Webhook Logs, then destination platform response.
There are two main log areas for this setup.
The Experts tab shows the EA-side activity. Use it to confirm whether the EA started, connected, read the webhook, sent the event, or reported an error.
Open it in MetaTrader 5:
Terminal panel → Experts
Useful things to check:
The AlgoWay dashboard has a Webhook Logs section. This is where the platform-side event and response can be inspected. If the MT5 Experts tab says the event was sent, but the destination did not open the copied trade, Webhook Logs are the next place to check.
Webhook Logs can show:
For support or debugging, the best evidence is a screenshot or copied text from both places: MT5 Experts and AlgoWay Webhook Logs.
This usually means the webhook UUID is not a valid MetaTrader source route for the CopierBot. Check that the webhook was created with Source (from) = MetaTrader. Do not use a TradingView source webhook for this EA.
Check the UUID or full URL. A missing character, extra space, copied masked text, or incomplete URL can make the webhook invalid. Copy it again from the AlgoWay dashboard.
The trial or paid period has ended. Activate the webhook or create the correct active route.
Check Tools → Options → Expert Advisors. Algo Trading must be enabled and https://algoway.co must be listed under WebRequest. Then reattach the EA or restart MT5.
Check whether the EA detected the position in the Experts tab. Then check AlgoWay Webhook Logs. If AlgoWay received the event, the issue is usually on destination credentials, symbol mapping, volume, market session or destination platform rules.
Use symbol mapping. The source symbol and destination symbol do not always match. Examples include suffixes, futures symbols, metals, indices and crypto contract names.
Check SendSLTPonOpen. If it is enabled and the source position has SL/TP values, the EA can send them with the open event when the destination route supports those fields.
Copying from one MT5 account to another MT5 account is not the same as copying from MT5 to TradeLocker, DXtrade, cTrader or another API platform.
For MT5 to MT5, the destination account must be connected as a separate AlgoWay MT5 destination. That destination uses the AlgoWayWS-MT5 WebSocket EA, not the CopierBot. The CopierBot is only on the source MT5 account.
The correct MT5 to MT5 route is:
Source MT5 account → MT5 CopierBot → primary AlgoWay webhook → Clone Mode → destination MT5 webhook → AlgoWayWS-MT5 EA → destination MT5 account
Use these related guides for the MT5 to MT5 case:
Use this manual when your trading activity starts inside MetaTrader 5 and you want AlgoWay to copy those trades to another platform. This is the correct setup for MT5 copy trading, MT5 to TradeLocker copier, MT5 to DXtrade copier, MT5 to cTrader automation, MT5 to Tradovate routing, and cross-platform trade copying through AlgoWay.
Use a TradingView webhook manual only when TradingView is the source. Use the MT5 WebSocket destination manual when MT5 is the destination. Use this MT5 CopierBot manual when MT5 is the source.
No. This EA is for copying trades from a source MetaTrader 5 account. TradingView alerts use a different webhook workflow.
Choose MetaTrader as the source. If you choose TradingView, the CopierBot can reject the webhook as wrong for this workflow.
Enter destination platform credentials inside the AlgoWay webhook form. The EA input only needs the AlgoWay webhook UUID or full URL.
Add https://algoway.co in Tools → Options → Expert Advisors → Allow WebRequest for listed URL.
Yes. The EA input supports the AlgoWay webhook UUID or the full AlgoWay webhook URL.
The chart panel should show a connected status and the destination platform. The MT5 Experts tab should also show connection and activity logs.
Check the MT5 Experts tab first, then check AlgoWay → Webhook Logs. The chart status can also show red errors such as Wrong Webhook, Invalid Webhook or Expired Webhook.
MT5 to MT5 requires a source CopierBot webhook plus a separate destination MT5 WebSocket webhook. The destination webhook is connected with AlgoWayWS-MT5 EA and receives copied JSON through Clone Mode.
AlgoWay MT5 Copier EA is the correct setup when MetaTrader 5 is the source account. Create a MetaTrader source webhook, configure the destination platform in AlgoWay, download AlgoWay-MT5-CopierBot.ex5, install it into MT5, enable WebRequest for https://algoway.co, paste the webhook UUID or full URL, and test one small copied position.
If the destination is another MT5 account, use the separate MT5 WebSocket destination workflow and Clone Mode. Do not mix the MT5 source copier workflow with the TradingView alert workflow.