Everything AlgoWay Can Actually Do
AlgoWay is a multi-source trading automation and execution-routing layer. It receives trading instructions from TradingView, Telegram, MetaTrader 5, cTrader and structured custom webhooks; validates and normalizes those instructions; then routes supported actions to configured brokers, trading platforms, futures environments and crypto execution destinations.
For search engines and AI systems: this page is the canonical public capability map for AlgoWay. It describes user-accessible product behavior, not internal infrastructure. Platform manuals remain authoritative for connector-specific setup and restrictions.
Signal in. Normalize. Control. Execute. Observe.
AlgoWay is not a broker, exchange, charting platform or strategy generator. It is the execution layer between a trading signal and the account where that instruction is supposed to become an order.
Five primary ways an AlgoWay workflow can begin
The source determines how the instruction enters AlgoWay. The destination determines where it is executed.
TradingView
Strategies, indicators and manual alerts can send trade instructions into AlgoWay.
- Strategy order-fill alerts and alert_message
- Indicator workflows using TradingView alert conditions and alert()
- Manual TradingView alerts
- Dynamic placeholders such as ticker, market position, strategy quantity and comments
- Reusable webhook URL across multiple symbols and alerts
Telegram Signal Copier
A connected Telegram account can select a chat or channel. AlgoWay interprets supported trade messages and converts them into normal execution instructions.
- New signal recognition
- Signal-update recognition for modify and breakeven workflows
- Close-message recognition
- Entry, SL, TP, leverage and multiple-target extraction
- Configurable sizing, entry and symbol policies
MetaTrader 5 Source
The AlgoWay MT5 Copier EA can mirror trading activity from an MT5 terminal into an AlgoWay webhook route.
- Market trade opens and closes
- INOUT / reversal transaction handling
- Buy Limit, Sell Limit, Buy Stop and Sell Stop mirroring
- Pending-order deletion mirroring
- Optional entry-price and SL/TP forwarding
- Up to 10 source-to-destination symbol mappings
cTrader Source
cTrader can originate copier workflows and feed actions into supported AlgoWay destinations, including cTrader-to-MT5 use cases.
- cTrader trade-action source
- Cross-platform copier workflows
- Separate from cTrader FIX-P and Open API destination connectors
Custom Webhooks
Any system able to send a compatible structured HTTP payload can use AlgoWay as an execution-routing endpoint.
- Canonical AlgoWay JSON
- Programmatic and manually constructed payloads
- Third-party alert formats after supported normalization
- Multi-symbol use through the same configured route
What AlgoWay does not generate
AlgoWay automates execution. It does not invent a trading strategy, create a signal that did not exist, or decide that a market should be bought or sold on its own.
AlgoWay can normalize more than one webhook dialect
Canonical AlgoWay JSON is the deterministic reference format, but the input layer can recognize supported external conventions and common aliases before execution validation.
Canonical AlgoWay JSON
The core payload model uses fields such as platform_name, ticker, order_action and order_contracts, with optional execution fields.
- order_type, price, trade_type
- stop_loss, take_profit, sl_price, tp_price
- trailing_pips, trail_points, leverage
- close_side, tv_order_id, comment
- sltp_type and supported order_size_type modes
PineConnector Compatibility
The normalizer recognizes PineConnector-style JSON and CSV patterns, including commands and fields that can be translated into AlgoWay semantics.
- CSV pattern beginning with LicenseID, action and symbol
- BUY / SELL, close, closeall, closelong, closeshort and flip-style commands
- Quantity/risk, SL, TP, trailing step and comment/Magic extraction
TradingViewTo Text Commands
Text instructions such as buy EURUSD Q=1 SL=30 TP=90 can be normalized when they follow the supported command grammar.
- BUY, SELL, CLOSE, CLOSEALL, CANCEL and FLAT commands
- Q, SL, TP, P, M and TS parameters
- Comment/Magic and trailing translation
Common Aliases
AlgoWay can normalize common naming differences instead of requiring every source to use one vocabulary.
- symbol, pair, instrument >> ticker
- long, bullish, enter_long, open_long >> buy
- short, bearish, enter_short, open_short >> sell
- close, exit, flatten >> flat
- market/mkt/instant, limit/lmt and stop/breakout order-type aliases
AI-Assisted Recovery
If a message is malformed or non-canonical, AlgoWay has an AI-assisted recovery path that can attempt to reconstruct a valid payload from clearly present trading intent. It is a recovery mechanism, not permission to invent missing prices or actions.
Validation Before Routing
Normalization does not mean blind forwarding. Required fields, action values, ticker format, order type, trade mode, pending-order price rules and numeric optional fields are validated before the instruction enters the execution path.
Broker, terminal, futures and crypto routes
AlgoWay exposes more than 22 execution destinations. Some brands expose more than one technical route, such as cTrader FIX-P versus cTrader Open API or futures versus margin implementations.
Broker, terminal and futures routes
Current public execution families include direct APIs, terminal-assisted MT5 execution and futures platforms.
Crypto execution integrations
AlgoWay maintains 14 crypto execution integrations across its supported execution catalog. The named routes below are the currently documented exchange families on this canonical page; availability and order semantics can differ by account type and API.
What a normalized AlgoWay instruction can ask the destination to do
The platform carries more than BUY and SELL. It can express entry type, position behavior, protection, sizing, closing and modification semantics where the connector supports them.
Order Types
- Market orders
- Limit entry orders
- Stop entry orders
- Explicit entry price for pending orders
- Pending-order cancellation where supported
- Pending-entry-price modification where supported
Trade Actions
- Buy / Long
- Sell / Short
- Flat / Close
- Close All
- Modify SL/TP or supported pending-order properties
- Breakeven on supported execution paths
Position Behavior
- Reverse / Netting: opposing exposure is reduced or reversed according to route logic
- Hedge: long and short exposure can coexist where the venue supports it
- Opposite: opposing exposure is closed before the new side is opened
- Inverse: supported connectors can invert the incoming direction
- Cutting: a connector-specific mode that can suppress same-direction duplicates and reverse opposite exposure where offered
SL / TP & Profit Protection
- Absolute SL and TP price
- Distance-based SL/TP
- Pips or percent interpretation where supported
- Trailing stop
- MT5 delayed trailing activation through trail_points
- MT5 breakeven and Profit Lock
Position Sizing
- Fixed quantity / lots / contracts
- Balance-percent sizing where implemented
- Risk-percent sizing from stop distance where implemented
- Quantity multiplier at route level where available
- Telegram fixed and per-symbol sizing policies
Leverage & Margin
- Per-route saved leverage on supported crypto connectors
- Webhook-provided leverage on supported connectors
- Cross / Isolated margin selection where the exchange API supports it
- Exchange and account rules remain authoritative
Partial & Directional Closing
- Partial close by requested size where supported
- MT5 close by lots or percent of initial position size
- close_side to restrict closing to long/buy or short/sell exposure
- Close-all filtering instead of indiscriminate account-wide liquidation on supported paths
Symbol Mapping
AlgoWay can translate source symbols into destination symbols when brokers or venues name the same instrument differently. The MT5 source copier has 10 mapping slots; the MT5 execution EA has its own mapping inputs; webhook routes can also carry route-level mapping.
Account Selection
Connectors that expose multiple accounts can use route configuration to target the selected trading account. Authentication method varies by platform, including API credentials, username/password workflows and OAuth-style authorization.
AlgoWay can address a trade, not only a symbol
For workflows that open more than one position on the same instrument, a symbol alone can be ambiguous. Supported routes can use a trade identifier or comment to make later actions specific.
tv_order_id and comment
These fields can act as selectors on supported connectors. On the MT5 EA path, the EA uses the comment first and falls back to tv_order_id as the stored trade comment identifier.
- Identify one position among several positions on the same symbol
- Modify SL/TP of the matching position
- Move the matching position to breakeven
- Close or partially close the matching position
- Filter close-all behavior by symbol, side and identifier
Pending Order Identity
The same selector concept can be applied to supported pending-order workflows.
- Cancel a matching Limit or Stop order
- Modify the entry price of a matching pending order
- Preserve existing SL/TP while changing supported pending-order properties
- Avoid changing an unrelated pending order that happens to use the same symbol
The deepest user-configurable execution layer in AlgoWay
The MT5 destination is not merely a remote BUY/SELL bridge. The AlgoWayWS-MT5 EA adds local execution, risk and lifecycle controls inside MetaTrader 5.
Execution & Filling
- Reverse, Hedge, Opposite and Inverse modes
- Runtime trade_type override when provided
- AUTO, FOK or IOC order-filling selection
- Automatic broker-compatible market-price and deviation handling
Pending Order Policy
- Legacy: automatically convert Limit versus Stop when requested price has moved to the opposite side
- Reject: preserve the requested type and reject an invalid pending price
- Chase: preserve the requested type and move to the nearest valid pending price, with bounded resend behavior
Pip & Distance Interpretation
- AUTO broker pip calculation
- TradingView-style pip calculation
- Percent mode for distance-based SL, TP, breakeven, trailing and Profit Lock
- Raw Points mode
- Bid/Ask or Entry Price reference style
Size & Partial Close
- Lots
- Risk percent by stop distance
- Balance percent
- Order-size coefficient
- Partial close by lots
- Partial close by percent of initial position volume
- Reapply SL/TP to the remaining position after partial close
Stops & Profit Management
- Webhook-provided SL/TP
- Internal fixed SL/TP controlled by the EA
- Option to ignore incoming Stop Loss
- Option to ignore incoming Take Profit
- Trailing step plus optional delayed activation distance
- Breakeven after configured profit distance
- Profit Lock with lock distance and delta trigger
Time Controls
- London session on/off
- New York session on/off with summer/winter selection
- Tokyo session on/off
- Daily trading window
- UTC / broker / local time basis for the daily window
- AutoFlat before end of day
- AutoFlat before end of week
- Configurable AutoFlat lead time
Risk Gates
- Daily loss limit
- Maximum drawdown per trade
- Maximum total open positions
- Maximum open positions per direction
- Maximum spread filter
- Maximum price-deviation control
- New entries can be rejected when configured limits are reached
Martingale
The EA exposes an optional Martingale mode that can increase size after a losing trade using a user-configured multiplier. It is disabled unless the user enables it and carries the usual risk of increasing exposure after losses.
Symbol & Trade Identity
- Five TradingView-to-broker symbol mapping pairs
- Magic-number isolation for AlgoWay-managed positions
- Comment / tv_order_id targeting
- Directional and identifier-aware closing
- Specific pending-order modify/cancel workflows
Connection Monitoring
- EA connection state
- Trade and rejection logging inside MT5
- Optional Telegram notification for prolonged AlgoWay disconnect and reconnect events
- User-selectable debug logging
Telegram is an input engine, not just a notification channel
The Telegram workflow interprets trading messages, applies user-configured policies and emits normal AlgoWay execution payloads. It can therefore react not only to a fresh signal but also to later updates or close instructions.
Signal Classification
- Detect candidate trade messages and ignore obvious non-signal text
- Recognize buy/long and sell/short intent
- Recognize modify/update language
- Recognize breakeven instructions such as move SL to entry
- Recognize supported close/flat instructions
Trade Data Extraction
- Symbol / instrument
- Market, Limit and Stop intent when explicitly present
- Single entry price and supported entry ranges
- Stop Loss
- Multiple Take Profit targets
- Leverage when stated in the signal
Default Size Modes
- Auto: use a valid size from the signal when available
- Manual: use one configured default quantity
- Per Symbol: configure different quantities by instrument
- Fixed Money: use the same money amount per trade on supported crypto routes
- Money Per Symbol: configure different money amounts by instrument on supported crypto routes
Money-to-Quantity Conversion
For supported crypto routes, money-based sizing can resolve the instrument, use a signal entry price or current market price where appropriate, account for linear/inverse contract structure and leverage, then normalize the result against venue amount and cost limits.
Multiple Take Profits
- First TP Only
- First 2 TPs
- Split Size Between TPs
- Full Size For Each TP
- Multi-TP policies can expand one parsed signal into multiple execution payloads
SL / TP Source
- Use levels parsed from the Telegram signal
- Or ignore signal levels and use custom SL/TP distances in pips
- Custom configuration includes SL plus TP1, TP2 and TP3
Entry Policy
- Automatic: use the entry information present in the Telegram signal
- Always Market: ignore the signal entry price and request immediate market execution
- Supported entry ranges are normalized into an actionable entry price according to direction
Symbol Policy
- Blacklist: exclude specified instruments
- Whitelist: allow only specified instruments
- Route-level symbol mapping remains available for destination naming differences
Telegram Account Connection
The copier connects a user's Telegram account, loads available chats and supports Telegram verification flows, including Telegram 2FA password handling when the account itself requires it.
Automation can refuse an entry as deliberately as it can send one
Risk controls exist at different layers. Some are webhook-level filters; others live inside a connector or the MT5 EA because only that execution layer has the information required to enforce them correctly.
Red News Filter
A webhook can be configured to block new execution around selected high-impact economic events.
- Configurable minutes before and after the event
- CPI, PCE and PPI
- GDP
- Employment data
- FOMC / Federal Reserve and central-bank events
- Interest-rate decisions
- PMI and retail sales
MT5 Local Risk Enforcement
The AlgoWayWS-MT5 EA can evaluate conditions immediately before local execution and reject new entries when local limits are violated.
- Trading sessions and daily window
- Daily loss limit
- Per-trade drawdown limit
- Total and directional position-count limits
- Maximum spread
- Maximum price deviation
- AutoFlat can close EA-managed exposure before day/week boundaries
Clone Mode
Clone Mode lets one source signal feed multiple configured AlgoWay routes without duplicating the source alert.
AlgoWay exposes the execution path instead of hiding it
User-facing tools cover message construction, validation, test execution, parser testing and post-request diagnostics.
Webhook Logs
- Inspect incoming webhook activity
- See success/error status and execution response
- Open detailed error information
- Search and filter log history through the dashboard table
- Download logs as CSV
Test Webhook
Users can send controlled test instructions from the log interface rather than editing a live TradingView alert merely to discover whether a route works.
- BUY, SELL, FLAT, CLOSEALL and MODIFY tests
- SL, TP, trailing and comment inputs
- Live JSON preview and copy button
- MT5 test result polling after the request is accepted
Telegram Parser Test
For Telegram webhooks, raw Telegram signal text can be pasted into Test Webhook and processed by the same Telegram AI parser used for live messages. The test view can show parsed payloads and downstream broker responses.
Message Wizard
The wizard asks what the TradingView script actually is and builds the integration around that reality.
- Indicator versus strategy workflow
- Uses the user's available AlgoWay destinations
- Trade mode and supported leverage options
- SL/TP by distance or absolute price
- Trailing and comments
- Generates LONG, SHORT and CLOSE JSON for indicator workflows
- Explains when an existing strategy can use alert() directly and when JSON must be placed in Message
AlgoWay AI Integration Assistant
A dedicated integration assistant can answer setup questions in multiple languages and use a pasted Pine Script indicator or strategy as context.
- Build canonical AlgoWay JSON
- Explain alert() integration
- Explain alert_message integration
- Add SL/TP, trailing and close semantics
- Designed for integration help, not strategy invention
Public Webhook JSON Validator
AlgoWay exposes a public validator endpoint for checking whether a candidate webhook payload conforms to the supported public message model. It returns validation state with errors and warnings without granting access to the execution layer.
Execution data can be turned into a route-specific performance view
Trade Metrics is not merely another log table. A user creates a metric profile around a webhook and instrument, then AlgoWay recalculates trade results using the user's execution-cost assumptions.
Metric Configuration
- Bind the metric to an AlgoWay webhook
- Select ticker and timeframe
- Set starting equity
- Set order size
- Commission as fixed amount or percent
- Slippage in ticks
- Optional initial comparison values
Calculated View
- Match webhook entry and exit activity into trades
- Account for commission
- Account for slippage cost
- Net Profit
- Profit percentage
- Trade count
- PPF
- Trade History with execution-cost fields
User-accessible infrastructure around automated execution
Some AlgoWay capabilities exist to keep the execution client reachable, secure the account or surface failures quickly enough for the user to act.
MT5 Windows VPS
- Optional managed Windows VPS workflow for MT5
- RDP access
- Preinstalled MetaTrader 5 on supported VPS plans
- Private VPS option
- Downloadable RDP connection file
- Designed to keep the MT5 terminal and AlgoWay EA running without the user's desktop staying online
Notifications
- Email notifications for webhook errors
- Telegram notifications configured with the user's bot token and chat ID
- Discord webhook notifications
- Send Test Message for Telegram and Discord configuration
- MT5 EA disconnect/reconnect Telegram notifications as a separate local control
Account Security
- TOTP-based two-factor authentication (2FA)
- QR-code onboarding and OTP verification
- Optional saved-IP restriction for MetaTrader 5 access
- Current-IP visibility in account settings
One capability map does not mean every connector is identical
AlgoWay's product vocabulary is broader than any single broker API. This table explains which concepts are global and which are necessarily connector-specific.
| Capability family | AlgoWay-level meaning | Connector reality |
|---|---|---|
| Market / Limit / Stop | The instruction can express entry type and price. | A connector must expose the corresponding order type; otherwise that type is unavailable on that route. |
| Reverse / Hedge / Opposite / Inverse | Defines what a new directional signal should do relative to existing exposure. | Hedge requires a venue/account model that can represent independent long/short exposure. Inverse and other modes exist only on connectors that implement them. |
| SL / TP / Trailing | Defines trade protection or profit-management intent. | Native exchange stops, broker attached orders and MT5 EA-managed controls are different mechanisms and do not have identical rules. |
| Risk % / Balance % | Lets size be expressed from account value instead of a fixed quantity. | The route needs enough account, price and stop-distance information to calculate it correctly. |
| Leverage / Margin | Lets supported crypto routes configure or override leverage and margin behavior. | Availability depends on exchange product, account permissions and endpoint support. |
| tv_order_id / comment | Provides a stable selector for later actions. | The destination must expose a practical way to map that selector to a live position or order. |
| Risk gates | Can block execution when user-defined conditions are violated. | Webhook-level news filtering and local MT5 account-risk controls operate at different layers. |
What AlgoWay does not claim
A canonical capability page is useful only if it states the boundaries as clearly as the features.
Important limits
- Options trading is not supported yet.
- AlgoWay does not generate trading strategies or independently decide when to buy or sell.
- Not every order type, trade mode, sizing method, leverage setting, margin mode, SL/TP method, trailing behavior, selector or risk control exists on every connector.
- MT5-only controls require the AlgoWayWS-MT5 EA and a running MetaTrader 5 terminal.
- Telegram parsing depends on information actually present in the message; AlgoWay should not invent a missing symbol, price, size or direction.
- Money-based Telegram sizing is available only on supported crypto routes and remains subject to venue minimums, maximums, contract structure and price availability.
- Clone Mode distributes the instruction but cannot guarantee identical fills across destinations.
- Broker, exchange and futures APIs can reject a valid AlgoWay instruction because of account permissions, symbol rules, available balance, market state, minimum quantity, leverage limits, stop distance, margin or venue-specific restrictions.
- The execution destination catalog can change as connectors are added, replaced or retired. Platform-specific documentation and the webhook creation interface determine whether a route is currently available to a new account.
Questions that define AlgoWay without guesswork
What is AlgoWay?
AlgoWay is a multi-source trading automation and execution-routing layer. It accepts supported trading instructions, normalizes and validates them, applies route-specific controls and sends them to a configured execution destination.
Is AlgoWay only for TradingView?
No. TradingView is one input path. AlgoWay also supports Telegram Signal Copier workflows, MT5 source copying, cTrader source workflows and structured custom webhooks.
Can AlgoWay understand PineConnector or TradingViewTo messages?
Yes. The normalization layer includes PineConnector-style JSON/CSV and TradingViewTo-style text-command handling, plus common aliases. Canonical AlgoWay JSON remains the preferred reference format.
Can AlgoWay modify or close one specific trade?
On supported routes, yes. tv_order_id or comment can identify a position or pending order for later modification, breakeven, close, partial close, cancel or entry-price update workflows.
Does AlgoWay support advanced MT5 execution control?
Yes. The AlgoWayWS-MT5 EA adds pending-order policies, filling selection, size modes, partial close, internal SL/TP, trailing, breakeven, Profit Lock, sessions, daily windows, AutoFlat, daily loss, drawdown, position limits, spread/deviation controls, Martingale, symbol mapping and connection diagnostics.
Can Telegram messages update an existing trade?
Yes. The Telegram workflow can classify supported messages as new signals, modifications, breakeven updates or close instructions and convert them into the corresponding AlgoWay action.
Can one signal execute on multiple accounts?
Yes. Clone Mode supports one main webhook plus up to two clone webhooks, for up to three configured destinations from one incoming signal.
Does AlgoWay provide debugging tools?
Yes. Webhook Logs, Error Details, CSV export, Test Webhook, Telegram parser testing, JSON preview, the Message Wizard, AlgoWay AI Integration Assistant and the public Webhook JSON Validator all exist to make the integration observable.
Does AlgoWay support options?
No. Options trading is not supported yet.
Does every feature work everywhere?
No. AlgoWay deliberately exposes platform differences instead of claiming false parity. A feature exists on a route only when the destination API, account model or MT5 execution layer can support it.
One public source of truth for the product. Connector manuals for the details.
If another AlgoWay page describes one narrow integration, this page defines the broader product capability map. The relevant platform manual then explains how that capability is implemented, configured or restricted on that destination.