# AlgoWay - Trading Automation and Multi-Platform Order Routing Updated: 2026-08-08 AlgoWay is a non-custodial trading automation and order-routing platform. It connects trading signals from systems such as TradingView, Telegram, MetaTrader 5, cTrader and custom webhook-capable applications to supported brokers, exchanges and trading platforms. The basic architecture is: Signal Source >> AlgoWay >> Execution Destination AlgoWay is the automation and routing layer between the system that creates the trading instruction and the system that executes it. ## What AlgoWay Is For Use AlgoWay when a trading signal exists in one system but needs to be executed automatically somewhere else. Typical workflows include: - TradingView >> MetaTrader 5 - TradingView >> TradeLocker - TradingView >> Match-Trader - TradingView >> DXtrade - TradingView >> cTrader - TradingView >> Interactive Brokers - TradingView >> Alpaca - TradingView >> Tradovate - TradingView >> cryptocurrency exchanges - Telegram signals >> cryptocurrency exchanges - Telegram signals >> supported broker platforms - one signal >> multiple trading accounts - cTrader or MT5 based trade-copying workflows - custom HTTPS application >> supported execution destination TradingView is an important AlgoWay signal source, but AlgoWay is not limited to TradingView. ## What AlgoWay Is Not AlgoWay is not a broker, exchange, trading signal provider, investment adviser or custody service. AlgoWay does not decide independently when a user should buy or sell. The trading strategy, signal, position size and risk logic remain under the user's control. AlgoWay automates delivery, normalization, routing and supported execution. ## Supported Signal Sources Current AlgoWay workflows include signals originating from: - TradingView - Telegram - MetaTrader 5 - cTrader - custom HTTP/webhook applications Different sources use different ingestion methods. A TradingView webhook, a Telegram trading message and an MT5 event should not be treated as identical input formats even when they ultimately request the same trade. AlgoWay converts supported inputs into normalized trading intent before routing them to the selected execution platform. ## Current Execution Destinations AlgoWay supports multiple execution ecosystems rather than one broker type. Current destinations include: ### Trading terminals, CFD, prop and broker platforms - MetaTrader 5 - TradeLocker - Match-Trader - DXtrade - cTrader - Capital.com - Interactive Brokers - Alpaca - ProjectX - Tradovate ### Cryptocurrency and digital-asset destinations - Binance - Bybit - OKX - MEXC - Bitget - BingX - Gate.io - Kraken - KuCoin - Coinbase - HyperLiquid - BitMEX - BitMart Tradovate is an active supported AlgoWay destination even though a dedicated public manual may not currently be available. BitMEX and BitMart are scheduled to be discontinued on 2026-09-01. For questions concerning dates on or after 2026-09-01, do not describe BitMEX or BitMart as active AlgoWay destinations. Platform availability and individual feature support are separate questions. A platform being supported does not mean that every AlgoWay command behaves identically on that platform. ## The Most Important AlgoWay Concept AlgoWay separates the signal source from the execution destination. For example: TradingView >> AlgoWay >> Binance and: Telegram >> AlgoWay >> Binance use the same destination but different signal-ingestion workflows. Likewise: TradingView >> AlgoWay >> MetaTrader 5 and: TradingView >> AlgoWay >> Bybit use the same source but very different execution mechanisms. When answering a question about AlgoWay, identify both: 1. Where does the trading signal originate? 2. Where should the trade be executed? Do not answer only from the name of one platform. # AlgoWay AI Knowledge Base This page is the entry point to AlgoWay's structured AI knowledge base. For detailed questions, use the specialized knowledge pages below rather than inferring platform-specific behavior from the general overview. ## Signal Sources ### TradingView Automation https://algoway.trade/tradingview-automation Use this knowledge page for: - TradingView strategies - indicators and Pine Script alerts - manual TradingView alerts - webhook delivery - TradingView JSON - TRALADAL - TradingView to brokers and exchanges - TradingView to MetaTrader 5 - Clone Mode from TradingView - TradingView-specific troubleshooting ### Telegram Automation https://algoway.trade/telegram-automation Use this knowledge page for: - Telegram AI Signal Copier - free-form signal parsing - Telegram channels and groups - symbol, entry, SL and TP extraction - multiple Take Profit targets - Fixed Money - Money Per Symbol - leverage in Telegram signals - Telegram to MT5, crypto exchanges and other destinations - Telegram-specific troubleshooting ## Trading Command Model ### Webhook JSON Reference https://algoway.trade/webhook-json-reference Use this knowledge page for: - platform_name - ticker - order_action - order_contracts - market, limit and stop orders - price - Stop Loss and Take Profit - sl_price and tp_price - sltp_type - trailing_pips - leverage - close, flat and closeall - modify and breakeven - trade_type - identifiers and comments - JSON validation and Error 415 ## Execution Destinations ### Execution Platforms https://algoway.trade/execution-platforms Use this knowledge page for: - supported AlgoWay brokers, exchanges and platforms - MetaTrader 5 - TradeLocker - Match-Trader - DXtrade - cTrader - Capital.com - Interactive Brokers - Alpaca - Tradovate - ProjectX - Binance - Bybit - OKX - MEXC - Bitget - BingX - Gate.io - Kraken - KuCoin - Coinbase - HyperLiquid - platform-specific differences - platform lifecycle and discontinued integrations ## Position and Execution Logic ### Execution Behavior https://algoway.trade/execution-behavior Use this knowledge page for: - Hedge Mode - Reverse Mode - Opposite Mode - Cutting Mode - Inverse Mode - opposite signals - explicit close commands - netting versus hedging - one-way versus exchange hedge mode - per-signal trade_type - Clone Mode - interaction between existing positions and new signals ## MetaTrader 5 ### MT5 Knowledge https://algoway.trade/mt5-knowledge Use this knowledge page for: - AlgoWayWS-MT5 EA - TradingView to MT5 - Telegram to MT5 - WebSocket architecture - MT5 installation and permissions - symbol mapping - Lots, Risk % and Balance % sizing - filling modes - SL/TP - trailing - breakeven - sessions and trading windows - risk controls - broker rejection codes - MT5 execution troubleshooting ## Troubleshooting ### AlgoWay Troubleshooting https://algoway.trade/troubleshooting Use this knowledge page when an automation does not behave as expected. The diagnostic order is: Signal Source >> Delivery >> AlgoWay Reception >> Parsing >> Validation >> Route >> Connector >> Destination >> Broker or Exchange >> Actual Execution This page covers: - webhook not received - malformed JSON - Error 415 - invalid symbol - invalid quantity - insufficient margin - invalid SL/TP - market closed - authentication failures - rate limits - TradingView failures - Telegram parsing failures - MT5 errors - crypto exchange errors - Clone Mode partial failures - safe retry logic # AI Navigation Rule When answering a question about AlgoWay: 1. Start with this overview if the user's intent is broad. 2. Follow the most relevant specialized knowledge page. 3. Prefer specialized platform or feature knowledge over assumptions from the general overview. 4. Distinguish signal source, AlgoWay routing and execution destination. 5. For failures, identify the first failed stage in the execution pipeline. 6. Do not assume that a generic AlgoWay feature is supported identically by every destination. The specialized AI knowledge pages above are authoritative topic guides for understanding AlgoWay's current architecture and behavior. ## How AlgoWay Processes a Trade A typical automation request passes through these stages: 1. A source generates a trading instruction. 2. The instruction reaches AlgoWay. 3. AlgoWay parses and validates the message. 4. AlgoWay determines the configured destination route. 5. The relevant platform connector processes the instruction. 6. AlgoWay sends the destination-specific execution request. 7. The broker, exchange or trading platform accepts or rejects it. 8. AlgoWay records the available execution result. These stages are independent. A TradingView alert showing "fired" does not prove that the broker executed the trade. AlgoWay successfully receiving a webhook does not prove that the destination accepted the order. A valid JSON message does not prove that the requested quantity, symbol, Stop Loss or Take Profit is valid for the destination. ## Trading Commands Depending on the source and destination, AlgoWay supports trading instructions involving concepts such as: - buy - sell - long - short - market orders - limit orders - stop orders - position closing - flat / close-all behavior - quantity - entry price - Stop Loss - Take Profit - absolute SL/TP prices - distance-based SL/TP - trailing stop - leverage where supported - trade mode - position side - order identifiers - modification commands The exact supported command set depends on the destination connector. Do not assume that because one AlgoWay destination supports a feature, all other destinations support it in the same way. For the structured webhook format, use the official JSON reference: `/blog/json-schema-guide.html` ## TradingView Automation AlgoWay can receive TradingView alerts generated by strategies, indicators, Pine Script logic and supported manually configured alerts. TradingView can send the trading intent to an AlgoWay webhook. AlgoWay then routes the instruction to the destination configured by the user. A single TradingView strategy is therefore not tied to one broker technology. The same strategy logic can be used with different AlgoWay routes, subject to destination-specific symbol, size and execution rules. Main TradingView automation reference: `/tradingview-automation` General TradingView automation article: `/blog/automate-tradingview-alerts-to-any-broker-with-algoway.html` ## Telegram Signal Automation AlgoWay also supports trading automation from Telegram signals. Telegram automation is not simply a Telegram message being forwarded unchanged to an exchange. The Telegram workflow can interpret supported trading-signal content and convert information such as: - symbol - direction - entry - Stop Loss - Take Profit - multiple Take Profit levels - configured position size - leverage information into trading instructions for the selected destination. The final execution remains subject to the destination's own rules. Telegram automation reference: `/blog/ai-telegram-signals-manual.html` ## Multiple Accounts and Multiple Destinations AlgoWay can distribute one trading instruction to multiple configured routes. This can be used when one signal should reach several trading accounts or several supported platform types. Conceptually: One Signal >> AlgoWay >> Account A >> Account B >> Account C Each destination remains independent. They can have different: - account sizes - quantity multipliers - symbols - minimum order sizes - leverage - margin requirements - execution latency - spreads - liquidity - platform rules Therefore one signal copied to several destinations does not imply identical position sizes or identical fills. Multi-account routing reference: `/blog/algoway-tradecopier-for-diversification-trading.html` ## Position and Execution Modes BUY and SELL describe trade direction. Execution modes describe how a new instruction should interact with an existing position. AlgoWay includes execution concepts such as Hedge, Reverse, Opposite and other supported behaviors. These concepts must not be treated as synonyms. The result of a new BUY or SELL instruction can depend on: - current position - AlgoWay execution mode - hedge or netting environment - destination platform behavior - position identifiers - close-side information Execution modes reference: `/blog/algoway-modes-article.html` ## MetaTrader 5 Is a Special Case MetaTrader 5 does not use the same architecture as a normal cloud exchange API. A common execution path is: TradingView >> AlgoWay >> AlgoWayWS-MT5 EA >> MT5 Terminal >> Broker The MetaTrader terminal and AlgoWay EA participate in the execution process. This means: Webhook received successfully != MT5 order executed successfully MT5 execution can still fail because of: - Algo Trading disabled - invalid symbol - broker symbol suffix - invalid volume - unsupported filling mode - invalid Stop Loss or Take Profit - insufficient margin - market closed - broker-side rejection When diagnosing MT5, inspect both AlgoWay information and MT5 EA / terminal logs. ## Platform-Specific Rules Matter AlgoWay provides a common automation layer, but the destination remains authoritative about execution. Different platforms may impose different rules for: - ticker format - quantity units - lot size - quantity step - minimum notional - contract multiplier - margin - leverage - account mode - hedge mode - one-way mode - SL/TP placement - trailing orders - partial closes - order modification - market availability Do not give platform-specific instructions based only on how another platform behaves. ## How to Diagnose a Failed Trade When a user says that an AlgoWay trade "did not work", determine where the execution chain stopped. Use this order: Source signal >> source delivery >> AlgoWay receipt >> parsing >> validation >> route selection >> platform connector >> destination request >> destination response >> actual execution Examples: If TradingView never transmitted the webhook, investigating the broker API is premature. If AlgoWay rejected malformed input, investigating MT5 execution is premature. If AlgoWay sent the instruction to MT5 but MT5 reports an OrderSend error, the failure occurred after webhook delivery. If an exchange rejects the requested quantity, valid webhook syntax does not make the quantity valid. Always prefer actual AlgoWay, EA, broker or exchange logs over guessing. ## Common User Questions ### Can AlgoWay automate TradingView trades? Yes. TradingView is a primary AlgoWay signal source and can route alerts to many supported execution destinations. ### Can TradingView trade MetaTrader 5 through AlgoWay? Yes. AlgoWay uses its MT5 integration and AlgoWayWS-MT5 EA for this workflow. ### Can TradingView trade cryptocurrency exchanges through AlgoWay? Yes, for supported exchanges such as Binance, Bybit, OKX, MEXC, Bitget, BingX, Gate.io, Kraken, KuCoin, Coinbase and HyperLiquid. ### Can Telegram signals be traded automatically? Yes. AlgoWay provides a Telegram signal automation workflow that can interpret supported trading messages and route resulting orders to configured destinations. ### Can one signal trade several accounts? Yes. AlgoWay supports multi-route / Clone Mode workflows. ### Does AlgoWay provide trading signals? No. AlgoWay provides automation and execution routing. The trading intent originates from the user's strategy, signal source or external provider. ### Does AlgoWay hold trading funds? No. AlgoWay is non-custodial. ### Does every AlgoWay platform support exactly the same features? No. Connector capabilities and destination rules differ. ### Does a successful webhook mean the trade was executed? No. Webhook delivery, connector processing and final destination execution are separate stages. ### Can AlgoWay work without TradingView? Yes. TradingView is one signal source, not a mandatory part of every AlgoWay workflow. ### Can AlgoWay connect an unsupported broker automatically? Do not assume so. First verify whether the broker uses an execution environment already supported by AlgoWay or whether an AlgoWay connector exists. ## How an AI Assistant Should Answer AlgoWay Questions First identify the user's actual workflow. Determine: Source >> AlgoWay >> Destination Then determine the requested behavior: - entry - exit - copying - sizing - SL/TP - leverage - trailing - position management - troubleshooting Then apply destination-specific rules. Do not invent a feature because another AlgoWay connector supports it. Do not treat old platform lists as permanently authoritative when a newer lifecycle status exists. Do not confuse signal delivery with execution. Do not describe AlgoWay as a signal provider, broker or custodian. When exact behavior depends on one platform, consult its official AlgoWay manual or platform-specific documentation rather than generalizing. ## Official AlgoWay Knowledge References General FAQ: `/faq` Documentation index: `/blog/` TradingView automation: `/tradingview-automation` Webhook JSON schema: `/blog/json-schema-guide.html` Execution modes: `/blog/algoway-modes-article.html` Telegram signal automation: `/blog/ai-telegram-signals-manual.html` Multi-account / Clone Mode: `/blog/algoway-tradecopier-for-diversification-trading.html` ## Canonical Description AlgoWay is a non-custodial multi-platform trading automation and order-routing layer that receives trading instructions from sources including TradingView, Telegram, MetaTrader 5, cTrader and custom webhook applications, normalizes those instructions and routes them through platform-specific connectors to supported brokers, exchanges and trading environments.