$9/month
Monthly subscription. Automate alerts, configure execution and inspect order responses.
Your TradingView strategy places orders on your TradeLocker broker or eligible prop firm account. Control position size, SL/TP and trade direction without a VPS or desktop bot.
14-day free trial for eligible new connections · Unlimited alerts · One account per regular subscription
Illustrative execution workflow
Cloud-based connection. Illustrative signal; the broker determines execution and fills.
Straightforward pricing
One regular subscription covers one trading account with unlimited TradingView alerts and symbols.
Monthly subscription. Automate alerts, configure execution and inspect order responses.
Annual subscription for the same account. Save $18 compared with monthly billing.
Available for eligible new connections. Test your account before committing.
Each destination requires a separate active connection unless covered by All-in-One ($69/month or $690/year). TradingView and broker charges are separate. Telegram Signal Copier is a separate subscription.
Funded and evaluation accounts
Use your own TradingView strategy on a TradeLocker account where the firm permits external automated execution.
TradeLocker is an available CFD platform. Check FTUK account rules.
TradeLocker is available for CFD accounts. Check Atlas Funded account rules.
Availability and automation permissions depend on program and location. Check E8 Markets account rules.
Platform support does not establish permission to automate a particular account. Check the firm’s current rules before connecting.
One strategy, multiple accounts
Clone Mode distributes the same instruction to independently configured accounts without duplicate alerts.
Keep your existing TradingView strategy and webhook.
Configure each destination's symbol mapping, trade mode and sizing.
One primary route and up to two additional configured routes in standard Clone Mode.
Clone Mode copies webhook signals, not manual trades. Execution results can differ across accounts.
The connection
TradingView is where your strategy identifies an opportunity. TradeLocker is where your broker holds the execution account. AlgoWay connects them with a webhook so you do not have to copy every alert into a manual order.
Use a strategy, Pine Script indicator or manual alert to generate an instruction when your own trading conditions are met.
A JSON message carries the symbol, action, size and any supported risk settings to a dedicated AlgoWay route.
AlgoWay applies the connection settings, then forwards the supported instruction to your selected broker environment and account.
Step-by-step setup
You do not need to write a connector or run your own server. Configure the destination account once, then use the webhook URL generated for your route.
Create an AlgoWay account, open your dashboard and add a webhook. Choose TradingView as the source and TradeLocker as the destination platform.
Enter the demo or live platform URL, email, password, broker server and numeric Account ID. Select the trade mode and check symbol mapping and quantity settings.
Copy your unique AlgoWay webhook URL. In a TradingView alert, paste the JSON order message under Message and enable Webhook URL under Notifications.
Send a small alert to a demo account, check the AlgoWay webhook logs and confirm the resulting position or rejection in TradeLocker. Test entry, close and opposite-direction behavior before going live.
Why use AlgoWay
Connecting TradingView to TradeLocker involves more than a URL. A real trading route must understand the destination account, the broker's symbols and the intended position behavior.
Receive alert instructions and route them to TradeLocker without keeping your personal computer, VPS or an MT5 Expert Advisor running.
Choose Hedge, Reverse, Opposite or Inverse according to your trading logic and the position rules of your TradeLocker account.
Connect alerts to the actual instrument names offered by the broker, instead of assuming every TradeLocker environment uses the same catalog.
Configure order-size handling and use supported stop-loss and take-profit inputs. Verify the contract size and broker stop requirements before live trading.
Set up independent webhook routes for different TradeLocker environments or accounts, each with its own connection and trading settings.
See whether an alert reached AlgoWay and investigate validation errors or broker-side rejections using the webhook log and the TradeLocker result.
Platform capabilities
TradeLocker is provided through different brokers and prop firms. These capabilities describe the AlgoWay routing layer; instruments, allowed position modes and execution depend on the specific account.
AlgoWay does not guarantee trading latency, fills, broker availability or account eligibility. Review your broker's trading conditions and any prop firm's automation rules.
Webhook message
AlgoWay accepts a compact TradingView webhook payload. The route you create in the dashboard identifies the destination account; the JSON identifies the symbol, order action and amount.
The example sends a market buy instruction for EURUSD. Replace the illustrative quantity with one that is valid for your TradeLocker broker. Do not assume that a CFD quantity is equivalent to the same number of MT5 lots.
Additional route-supported fields can handle Stop Loss, Take Profit, order type and linking identifiers. Start with a simple test, then add risk fields after confirming that the basic order is accepted.
See TradeLocker JSON and SL/TP examples →{
"platform_name": "tradelocker",
"ticker": "EURUSD",
"order_action": "buy",
"order_contracts": 0.1,
"order_type": "market"
}Broker and prop trading accounts
TradeLocker can be used with personal brokerage accounts and funded-account environments. Two accounts may show the same interface yet use different servers, tradable instruments, order-size limits and hedging restrictions.
Automate alerts for the symbols supported by your TradeLocker broker, including Forex pairs, indices and other CFDs available on that account. Confirm spreads, contract specifications, position sizes and stop distances.
Connect a TradeLocker prop firm account only when the firm's rules permit the intended automation. Account eligibility, daily loss restrictions and trading limits are controlled by the provider, not by AlgoWay.
Learn and verify
Follow a recorded setup and the written reference for account credentials, TradingView alerts and webhook troubleshooting. These resources cover the same AlgoWay TradeLocker connection described on this page.
See the TradeLocker connection, TradingView alert and order-routing workflow before configuring your own webhook.
Frequently asked questions
Clear answers about the connection, trial, supported execution modes and the account-specific limitations that matter during setup.
A TradingView alert by itself does not execute an order in TradeLocker. AlgoWay receives the TradingView webhook message, validates the instruction and routes it to the TradeLocker broker account connected to your webhook.
Create an AlgoWay webhook with TradingView as the source and TradeLocker as the destination, enter your TradeLocker server and account details, then paste the generated webhook URL and JSON alert message into TradingView. Test the route on demo before live use.
No VPS or MT5 Expert Advisor is needed for the TradeLocker connector. AlgoWay runs the webhook routing service in the cloud. The TradingView alert and the connected broker account must still be available.
Yes. Select the correct TradeLocker environment, broker server and numeric Account ID when setting up each connection. Availability of symbols and trading permissions depends on that broker account.
You can connect a TradeLocker account supplied by a prop firm when its credentials and broker environment are supported. Check the firm's automation rules, maximum order sizes and other account restrictions before trading.
AlgoWay accepts supported SL and TP fields in TradingView webhook JSON, including absolute price fields. The connected broker determines valid minimum distances and whether an order or modification is accepted.
The TradeLocker route provides Hedge, Reverse, Opposite and Inverse trade behavior selections. They are different modes, and the broker account's position rules determine what is accepted.
Separate AlgoWay webhook routes can be configured for separate destination accounts, with their own credentials, symbol mapping and size settings. Check each account individually; never assume that contract sizes or rules match.
Check the AlgoWay webhook logs and TradeLocker response. Common causes include an incorrect server or Account ID, unsupported symbol, invalid quantity increment, trade mode conflict or a stop loss too close to market.
AlgoWay offers a 14-day free trial to test a TradingView to TradeLocker webhook connection before configuring live automation.
TradingView webhook availability is determined by your TradingView subscription and its current feature limits. Confirm that your plan offers webhook URL notifications before creating the connection.
Start with a demo connection, test your alerts and check the execution logs. AlgoWay supplies the cloud webhook route; your strategy and brokerage account remain under your control.