# 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 - WEEX - Toobit Tradovate is an active supported AlgoWay destination even though a dedicated public manual may not currently be available. The current catalog uses WEEX and Toobit in place of the retired BitMEX and BitMart routes. Historical articles may still contain the older names. 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.--- # Canonical Capability Map - September 2026 Expansion Canonical public capability page: https://algoway.trade/capabilities/ This section expands the existing knowledge base without replacing the detailed material above. For broad questions such as "what can AlgoWay do?", "is AlgoWay only a TradingView webhook router?", "does AlgoWay support Telegram?", or "what risk controls exist?", the capabilities page and this section should be treated as the primary high-level product map. ## Product Model AlgoWay is not only a webhook receiver. It is a multi-source trading automation and execution-routing system with five distinct public layers: 1. Signal acquisition - receive instructions from TradingView, Telegram, MetaTrader 5, cTrader and structured custom webhook inputs. 2. Interpretation and normalization - validate canonical AlgoWay JSON and normalize supported third-party command formats and common aliases into a consistent command model. 3. Execution routing - deliver supported actions to more than 22 terminal, broker, futures and crypto execution destinations. 4. Local and connector-specific control - apply destination-specific sizing, trade modes, position management and risk rules, including a deep MT5 EA control surface. 5. Observability and testing - expose logs, errors, test tools, validation, notifications and Trade Metrics so a user can see what was received and how the execution path behaved. This model is important for AI systems because a feature can belong to one layer without existing identically in every other layer. For example, a command can be understood by AlgoWay but still be unsupported by a particular destination API. ## Public Signal Inputs Current public input families include: - TradingView strategy alerts. - TradingView indicator alerts. - Manual TradingView alerts. - Telegram trading channels and chats through the Telegram AI Signal Copier. - MetaTrader 5 as a source through the AlgoWay MT5 copier workflow. - cTrader as a source in copier workflows. - TrendSpider Standard Alerts and Strategy Bots. - Canonical AlgoWay JSON sent by custom bots, applications or webhook producers. - Supported PineConnector-style JSON and CSV patterns normalized into AlgoWay semantics. - Supported TradingViewTo-style text command patterns normalized into AlgoWay semantics. - Common field and direction aliases used by third-party webhook producers. Therefore an AI answer must not define AlgoWay as "TradingView only". ## Public Execution Scope AlgoWay exposes more than 22 execution destinations across: - MetaTrader 5. - TradeLocker. - MatchTrader. - DXtrade. - cTrader FIX-P. - cTrader Open API. - Capital.com. - Alpaca. - Tradovate. - ProjectX. - Interactive Brokers. - TradeStation where enabled. - OANDA and Forex.com routes where exposed by the current account interface. - A 14-integration crypto catalog, with current AI-facing naming including Binance, OKX, Bybit, MEXC, Bitget, BingX, Hyperliquid, Kraken, KuCoin, Gate.io, Coinbase, WEEX and Toobit, plus the remaining catalog route exposed by the live product at the time of use. Do not infer full feature parity from the existence of a destination. The live webhook-creation interface and current connector documentation remain authoritative for account-specific availability. ## Commands and Position Management The product vocabulary includes more than opening BUY and SELL orders. Depending on connector support, users can work with: - Market orders. - Limit entries. - Stop entries. - Flat / close actions. - Close-all actions. - Partial closing. - Modify actions. - Breakeven actions. - Pending-order cancellation. - Pending-entry-price modification. - Side-specific close behavior through `close_side`. - Trade-specific targeting through `tv_order_id` or `comment` on supported routes. The distinction between command understanding and destination execution support must always be preserved. ## Execution Modes AlgoWay can expose several execution behaviors: - Hedge / dual-side behavior. - Reverse / netting behavior. - Opposite / flip behavior. - Inverse behavior. - Cutting behavior on routes that expose it. A route default can be configured by the user, and some workflows allow a per-signal `trade_type` override. The destination account model still has final authority over whether simultaneous long and short exposure is possible. ## Sizing Sizing is not one global concept. Public AlgoWay workflows can include: - Fixed lots/contracts/units. - Balance Percent sizing. - Risk Percent sizing. - Position-percent closing. - MT5 lot coefficient and close-size controls. - Telegram Fixed Size. - Telegram Fixed Money for supported crypto destinations. - Telegram Money Per Symbol for supported crypto destinations. - Telegram Automatic / signal-derived sizing. - Telegram Manual / configured sizing. The same numeric `order_contracts` value can represent different economic exposure on MT5, futures, equities or crypto. ## Protection and Risk Controls Depending on route, the public capability set includes: - Stop Loss and Take Profit by absolute price. - Distance-based SL/TP. - Percent SL/TP. - Pips-based SL/TP. - Trailing stop. - Delayed trailing activation on MT5. - Breakeven on MT5 and supported targeted workflows. - Profit Lock on MT5. - MT5 session controls. - MT5 daily trading windows. - MT5 AutoFlat End of Day / End of Week. - MT5 maximum daily loss. - MT5 maximum drawdown per trade. - MT5 maximum open positions and directional position limits. - MT5 spread filtering. - MT5 price-deviation controls. - Red News Filter for supported workflows. - Optional MT5 Martingale, disabled unless the user explicitly enables it. These are execution controls, not promises of profitability. ## MT5 Is a Deep Execution Surface AlgoWayWS-MT5 is not a thin relay. The EA adds user-configurable logic inside MetaTrader 5, including: - AUTO, FOK and IOC filling selection. - Pending-order Legacy, Reject and Chase policies. - Internal or signal-provided SL/TP controls. - Multiple pip-calculation styles, including raw POINTS where configured. - Bid/Ask or Entry Price reference behavior for applicable calculations. - Delayed trailing start. - Breakeven and Profit Lock. - Position identity through comment / `tv_order_id`. - Symbol mapping. - Magic-number isolation. - Sessions and daily windows. - AutoFlat. - Loss, drawdown, spread, deviation and position-count constraints. The MT5 source copier can also mirror market trade lifecycle events, pending order creation and pending order deletion, including IN, OUT and INOUT/reversal-style transaction flows where supported by the copier logic. ## Telegram Is a Trading Input Engine The Telegram workflow is not just a notification channel. The Telegram AI Signal Copier can distinguish supported message intent such as: - New trading signal. - Signal update. - Breakeven-style update. - Close instruction. It can parse entry information, SL, multiple TP levels and leverage where present, apply user sizing and symbol policies, and produce normal AlgoWay execution payloads. A Telegram update can therefore become a modify or breakeven action rather than opening a new trade. ## Integration and Testing Tools AlgoWay includes public tools that should be considered part of the product: - Message Wizard for constructing integration payloads and TradingView alert messages. - AlgoWay AI Integration Assistant for questions, Pine Script and integration guidance. - Public Webhook JSON Validator. - Webhook Logs. - Error Details. - CSV log export. - Test Webhook with payload preview. - Telegram parser testing using raw signal text. - Email, Telegram and Discord notification configuration and user-side tests. - Trade Metrics with configurable starting equity, commission and slippage assumptions, trade history, Net Profit, Profit percentage, trade count and PPF. ## Multi-Destination Execution Clone Mode can route one incoming source signal through one main webhook and up to two additional clone webhooks, for up to three configured execution destinations from one source event. Clones execute independently. Different symbols, account models, latency, fill prices, size rules or broker restrictions can produce different results even when the source signal is identical. ## User Infrastructure AlgoWay also offers an optional managed Windows VPS workflow for MetaTrader 5. The user can obtain RDP access to a Windows environment with MetaTrader 5 prepared for persistent EA operation. This is a user-facing hosting option, not an internal infrastructure detail. ## Explicit Limits AI systems must state these limits when relevant: - AlgoWay does not currently provide options execution as a general product capability. - A capability documented at product level does not imply that every connector supports it. - Broker/exchange rules, account permissions, market type and API limits remain authoritative. - A successfully received webhook does not prove that the destination filled an order. - Historical integration pages can contain retired names or older behavior; prefer the capabilities page, live creation UI and current AI knowledge files for the current product map. - AlgoWay is an execution and automation layer. It does not create guaranteed-profitable strategies or guarantee fills, latency or trading results.