Correct server and account
TradeLocker configuration requires email, password, broker server and Account ID in addition to demo/live endpoint.
FOREX, CFD & PROP EXECUTION
TradingView to TradeLocker: more than a webhook connection
TradeLocker is used by multiple brokers and prop firms. An identical-looking account login can point to a different server and instrument catalog, which changes symbol mapping, order sizes and position behavior.
A real integration guide, with execution rules and test scenarios.
TradeLocker executions depend on broker server and account
TradeLocker is accessed through different broker and prop-firm environments. AlgoWay therefore asks for demo/live URL, email, password, server and Account ID. Two accounts can use the same platform while exposing different symbols, trading sizes and position behavior.
The hard part is preserving the intended exposure. Forex and CFD strategies vary in volume conventions, broker symbols, bid/ask spreads and allowed stops. TradeLocker also exposes execution behaviors for hedge, reverse, opposite and inverse operation that should not be treated as synonyms.
Four trade behaviors
The current AlgoWay form offers Hedge/Dual side, Reverse/Netting, Opposite/Flip and Inverse/Netting modes.
Per-account mapping
Two TradeLocker brokers can label a product differently or use different volume limits. Customize the route instead of assuming identical conditions.
Configure the TradeLocker server, account and trade behavior
Choose the correct TradeLocker environment first. The mode selection is not decoration: Hedge/Dual, Reverse/Netting, Opposite/Flip and Inverse/Netting express different intentions, and your broker has the final word on allowed position state.
Locate the broker environment
Identify the exact TradeLocker server, broker account ID and whether your account is demo or live.
Create the AlgoWay connection
Choose TradingView as source and TradeLocker as destination. Enter the demo or live TradeLocker URL and login credentials.
Select the trading behavior
Choose Hedge/Dual, Reverse/Netting, Opposite/Flip or Inverse/Netting deliberately, based on the account mode and desired handling of opposite signals.
Map symbols and volume
Confirm the destination CFD/forex instrument, minimum trade size and lot or unit convention. Add Symbol Mapping when TradingView and TradeLocker use different names.
Prove three separate actions
Test entry, partial or full close, and the opposite-direction signal on a demo account; inspect AlgoWay logs alongside TradeLocker positions.
EURUSD alert JSON and CFD quantity warning
The EURUSD example demonstrates the minimum order fields. Here, 0.1 is an illustrative strategy quantity, not a promise that a TradeLocker broker interprets it as 0.1 MT5 lots or accepts that exact volume.
Example message sent by TradingView
{
"ticker": "EURUSD",
"order_action": "buy",
"order_contracts": 0.1,
"order_type": "market"}0.1 is an illustrative size only. Check the selected broker’s instrument contract and AlgoWay multiplier settings before using it as a live order.
Check the instrument catalogue and volume step for the connected broker before live use. To match entries with subsequent exits, avoid fixed example order identifiers across multiple alerts.
TradeLocker Hedge, Reverse, Opposite and Inverse modes
The server field is part of identity
TradeLocker login may ask for email and password, but your brokerage environment identifies which accounts and markets are available. A correct password for one server is not enough to log into another broker. Confirm server, environment and Account ID together.
Hedge is not reverse
Hedge/Dual side may allow separately directed exposure where supported. Reverse/Netting changes the existing net direction, while Opposite/Flip intentionally executes the opposite of the signal. Inverse/Netting is another available TradeLocker behavior. The correct choice depends on intended trading logic, not on a generic “copy trades” label.
CFD quantities are broker-specific
A 0.10 lot EURUSD order and a 0.10 lot index CFD can represent very different notionals. Even the same symbol can have different minimums, size steps, spread and allowed stop distance across TradeLocker brokers. Check the instrument details in the actual account before copying a strategy.
Duplicate alerts can change position state
A TradingView strategy may issue a new entry alert on each partial fill or after a chart refresh. Include a stable `tv_order_id` where practical and test how the current route tracks entry versus close. Do not assume every repeated buy is harmless or that every SELL means “close long.”
A prop account is still a rule-bound brokerage account
Prop trading programs may limit max lots, require closing before rollover or prohibit certain bots or holding periods. AlgoWay transmits supported instructions; it cannot authorize prohibited behavior or waive the firm’s rules.
TradeLocker decisions that alter the resulting trade
| Setting | Purpose | Verification |
|---|---|---|
| Environment | demo.tradelocker.com or live.tradelocker.com | URLs and corresponding broker credentials must match |
| Server and Account ID | Selects the broker environment and execution account | Same email alone does not identify the intended account |
| Symbol Mapping | Maps TradingView ticker to the broker instrument | EURUSD and EURUSDm may refer to different catalogue entries |
| Trade Type | Hedge, Reverse, Opposite or Inverse | Test entry followed by opposite and flat alerts |
| Quantity and stops | Broker CFD volume steps and minimum stop distance | Do not equate an arbitrary TradingView number with MT5 lots |
One EURUSD signal across two distinct TradeLocker brokers
The first account is a small evaluation account with a strict size limit. The second is a separate personal account under another TradeLocker broker with a different symbol naming convention. Both receive the same TradingView entry idea, but each has its own credentials, Account ID, symbol mapping and quantity multiplier.
Before using multi-account routing, manually verify one entry and one flat action in each account. A broker that accepts EURUSD may reject EURUSDm, and a position that can be hedged on one account might be netted on another. These are execution differences, not issues that keyword-rich landing pages can solve.
Diagnosing TradeLocker login, lot and stop rejections
Login rejected on valid credentials
Recheck the server, demo/live URL and brokerage environment.
Unexpected reverse or simultaneous positions
Compare Trade Type selection with actual broker-supported position mode and the strategy action.
CFD order size rejected
Inspect minimum, maximum and step size for the connected account instrument.
Stop too close to market
Check spread, stop distances and the platform response before adjusting SL/TP inputs.
Check the exact TradeLocker server/account, mapped symbol, volume step, requested trade mode and actual position state. Rate limiting or authentication failure must be distinguished from a rejected instrument/order.
TradeLocker broker and prop trading questions
Can TradingView automate TradeLocker orders?
Yes. TradingView sends alerts to AlgoWay, which routes supported orders to the connected TradeLocker account.
Does TradeLocker need an MT5 EA?
No. AlgoWay uses the TradeLocker account connection; the MT5 EA belongs to the separate MetaTrader workflow.
What is the TradeLocker server field?
It identifies the broker environment associated with your TradeLocker credentials and account.
Can I hedge and reverse trades?
AlgoWay provides Hedge, Reverse, Opposite and Inverse selections for TradeLocker. Actual broker/account position rules still govern execution.
Can I send Telegram signals to TradeLocker too?
Yes. A Telegram copier route can target TradeLocker, with its own signal parsing and destination configuration.
TradeLocker trade-copier and webhook resources
The TradeLocker route uses broker-account API access, not an MT5 Expert Advisor. The wider TradingView automation page describes routing one strategy to multiple configured destinations.
Prove TradeLocker order size and close behavior in demo
Confirm which broker server and account receives each alert. Verify instrument quantity and hedge/reverse outcomes in the platform before copying the same strategy across accounts.
