Main clusters and core pages.
TradingView to DXtrade automation means sending a TradingView alert to an AlgoWay webhook URL and routing that structured signal into a DXtrade account. The alert comes from TradingView, AlgoWay receives and validates the JSON command, and the DXtrade route executes the supported trading action on the configured account.
This page is the dedicated AlgoWay guide for traders searching for TradingView to DXtrade, DXtrade webhook automation, TradingView alert to DXtrade, DXtrade trading bot, webhook autotrade bot for DXtrade, and automated trading on DXtrade with TradingView alerts.
The basic route is:
TradingView alert → AlgoWay webhook URL → AlgoWay DXtrade route → DXtrade account
Last updated: 2026-05-12 • Author: AlgoWay
To automate TradingView alerts to DXtrade with AlgoWay:
Minimal DXtrade JSON example:
{
"platform_name": "dxtrade",
"ticker": "{{ticker}}",
"order_action": "{{strategy.market_position}}",
"order_contracts": "{{strategy.order.contracts}}",
"price": "{{close}}"
}
DXtrade is a broker-side trading platform used by brokers, prop firms and trading environments that need web, mobile and multi-asset execution. A trader may have a DXtrade account at a broker or prop firm, while the trading strategy itself runs in TradingView.
TradingView can generate the signal. DXtrade holds the trading account. AlgoWay connects the two sides:
Strategy condition in TradingView → webhook JSON → AlgoWay parser → DXtrade order action
This is different from manual trading. It is also different from simply viewing TradingView charts inside a DXtrade interface. In webhook automation, the alert message carries the order instruction: buy, sell, flat, size, symbol, price, stop loss, take profit and supported route parameters.
TradingView sends an alert. It does not automatically know how your DXtrade broker expects authentication, account IDs, symbols, trade mode or order formatting. AlgoWay acts as the automation layer between TradingView and DXtrade.
AlgoWay helps with:
Open the AlgoWay dashboard and create a new webhook route for DXtrade.
The webhook URL format is usually:
https://algoway.co/your-webhook-uuid
DXtrade routes need account-specific information because the order must be sent to the correct broker environment and account.
| AlgoWay field | Example | Purpose |
|---|---|---|
| Platform | DXtrade | Selects the DXtrade connector route. |
| Quantity Multiplier | Absolute / 1 | Controls how the incoming TradingView order size is interpreted. |
| Trade Type | Hedge / Reverse | Controls how opposite-direction signals are handled by the route. |
| URL | https://dxtrade.yourbroker.com | The DXtrade environment URL provided by your broker or prop firm. |
| Login | Account login | The login used for the DXtrade account. |
| Password | Account password | The password for the DXtrade account. |
| Account ID | Numeric or broker-specific account identifier | Tells AlgoWay which DXtrade account should receive the order. |
After the DXtrade route exists in AlgoWay, create or edit the TradingView alert that will send the signal.
For many automated strategies, Once per bar close is easier to control than intra-bar execution. If your strategy intentionally needs faster action, test carefully with small size first.
AlgoWay reads the TradingView alert message as JSON. Keep the JSON valid and keep platform_name aligned with the route.
{
"platform_name": "dxtrade",
"ticker": "{{ticker}}",
"order_action": "{{strategy.market_position}}",
"order_contracts": "{{strategy.order.contracts}}",
"price": "{{close}}"
}
{
"platform_name": "dxtrade",
"ticker": "EURUSD",
"order_action": "buy",
"order_contracts": 1,
"price": "{{close}}"
}
{
"platform_name": "dxtrade",
"ticker": "XAUUSD",
"order_action": "sell",
"order_contracts": 1,
"stop_loss": 50,
"take_profit": 120,
"price": "{{close}}"
}
{
"platform_name": "dxtrade",
"ticker": "{{ticker}}",
"order_action": "flat",
"order_contracts": 999999,
"price": "{{close}}"
}
Full JSON reference: AlgoWay JSON schema guide.
A DXtrade automation route is not only about entry. Real alert automation also needs exit behavior and risk fields.
| Feature | JSON field | Use case |
|---|---|---|
| Buy / Sell | order_action |
Open or route directional entries from TradingView. |
| Flat / Close | order_action: "flat" |
Close the active position for the symbol where supported by route logic. |
| Size | order_contracts |
Pass strategy size, fixed size or route-controlled size. |
| Stop Loss | stop_loss / sl_price |
Define risk exit by offset or exact price where supported. |
| Take Profit | take_profit / tp_price |
Define target exit by offset or exact price where supported. |
| Trade Type | Dashboard setting | Controls hedge/reverse behavior at route level. |
In the TradingView alert window, open Notifications, enable Webhook URL, and paste the AlgoWay URL copied from the DXtrade route.
https://algoway.co/your-webhook-uuid
If the Webhook URL option is not enabled, TradingView may create the alert, but AlgoWay will not receive the signal.
Before live size, send a small test alert and inspect the result.
If AlgoWay logs do not update, the TradingView alert did not reach AlgoWay. If logs update but DXtrade does not execute, inspect the DXtrade response and the route configuration.
DXtrade environments are broker-specific. If the URL belongs to another broker or environment, login and execution can fail.
DXtrade login and account ID are not always the same value. Use the account ID shown in the DXtrade platform or provided by the broker.
The JSON message alone is not enough. Enable Webhook URL in the TradingView alert Notifications tab.
Missing quotes, broken braces, trailing commas or plain text can break the alert. See: How to fix AlgoWay webhook Error 415.
For this route, use "platform_name": "dxtrade". Do not reuse JSON from MT5, Binance or TradeLocker without changing the platform field.
TradingView symbols may not match the DXtrade broker symbol exactly. If the broker uses suffixes or a different symbol format, configure mapping or send the exact accepted ticker.
DXtrade route execution can fail if the size is below minimum, above maximum, not allowed for the instrument, or inconsistent with the account type.
If your strategy sends opposite signals, check whether the AlgoWay route is configured for hedge or reverse behavior. This affects how buy and sell signals interact with existing exposure.
AlgoWay supports DXtrade, but the same dashboard can also route TradingView alerts to other execution destinations.
| Route | Best for | Related guide |
|---|---|---|
| TradingView → DXtrade | DXtrade broker or prop-firm accounts. | This guide |
| TradingView → MetaTrader 5 | MT5 terminal-based execution. | MT5 setup guide |
| TradingView → TradeLocker | Modern broker-side TradeLocker accounts. | TradeLocker setup guide |
| TradingView → Match-Trader | Match-Trader broker accounts. | Match-Trader setup guide |
| TradingView → Binance / OKX / Bybit / MEXC | Crypto exchange execution. | JSON schema guide |
platform_name is dxtrade.Yes. TradingView can send a webhook alert to AlgoWay, and AlgoWay can route the structured command to a configured DXtrade account.
No. TradingView charting inside DXtrade is a charting feature. TradingView webhook automation is an alert-delivery and order-routing workflow from TradingView to AlgoWay to DXtrade.
Put valid JSON with "platform_name": "dxtrade", a ticker, order action, size and optional risk fields such as stop loss and take profit.
No. DXtrade automation does not use the MT5 EA route. It uses the DXtrade route configured in AlgoWay.
Check DXtrade URL, login, account ID, symbol, size, market status, route mode and the platform response in AlgoWay logs.
Yes. Create a trial route or use small test size, trigger an alert, and verify the payload and DXtrade response in AlgoWay logs.
TradingView to DXtrade automation is a practical webhook route: TradingView creates the signal, AlgoWay receives the JSON, and DXtrade receives the execution command through the configured route.
Start with one small test alert, verify the JSON in AlgoWay Webhook Logs, confirm the DXtrade response, and only then connect the final strategy or indicator for automated trading.