Automate
Send a TradingView alert to a TradeLocker account
TradeLocker is the platform forex and CFD prop firms hand out, and it connects with three fields: email, password and server. The rest of the path is the same as the futures brokers — with one difference worth knowing before you start, which is that a strategy is bound to one market and a CFD strategy can only be followed by CFD accounts.
Checked against Tradeus on 14 September 2026.
Before you start
- A TradingView account with 2-factor authentication enabled.
- Your TradeLocker email, password and the server your firm issued. A demo server is a perfectly good place to start.
- A Tradeus plan that includes the TradingView webhook — Algo or Unlimited.
The numbers
- Time TradingView waits for the receiver
- 3 seconds, then the request is cancelled
- Ports it will post to
- 80 and 443 only
- IPv6
- Not supported for webhooks
- Account requirement
- 2-factor authentication must be enabled
- What TradeLocker asks for
- E-mail, password, server
- What counts as one login
- Email, server and environment together
- Strategy market
- futures or cfd; it decides which accounts may follow
Step by step
What to do, in order.
- 1
Connect TradeLocker with email, password and server
TradeLocker asks for three fields and the server is the one people get wrong: the same email on a different prop firm's server is a different login entirely, and is claimed separately. Start on a demo server if you have one — everything here behaves identically on it and a malformed alert costs you nothing but the lesson.
- 2
Create the strategy as a CFD strategy
A strategy declares the market it trades — futures or cfd — and that choice decides which of your accounts may follow it. Create a cfd strategy for TradeLocker accounts. A futures strategy will simply refuse them, which is the correct behaviour and looks like a bug the first time.
- 3
Paste the URL and the ready-made message into a TradingView alert
Open the alert dialog on your chart, put the webhook URL in the Notifications tab's Webhook URL field, and paste the strategy's own alert message into the message box. Use the message Tradeus shows on the strategy rather than an example from anywhere else: it already has your passphrase filled in and it already sends the two fields that make a repeated alert harmless.
- 4
Subscribe an account to the strategy
Until an account follows the strategy, signals are recorded and nothing trades. This is the step people miss, and it is the single most common reason a first alert arrives, shows green in the event log, and moves no money. A strategy with no subscribers is a working endpoint with nowhere to send anything.
- 5
Set the size on that subscription
Size belongs to the subscription — one account following one strategy — not to the strategy. That is what lets one signal put a single contract on an evaluation and four on a funded account. Choose the alert's own quantity times a factor, a fixed number of contracts, a dollar amount of risk per trade, or a percentage of the balance.
- 6
Arm a daily loss limit before the first live signal
A daily loss limit is the cheapest insurance in the product, and the right moment to set it is before anything has traded rather than after something has. It sits on the account, so it holds whether the order came from this strategy, another one, or the copier.
- 7
Fire one alert manually and read the event log
Every signal is recorded, including the refused ones, and each refusal names its own reason — invalid passphrase, no subscription, outside the trading window, rounds to 0 contracts. Send one deliberate test alert and read what the log says about it. If the signal is not in the log at all it never arrived, which is a TradingView-side problem rather than anything to change here.
What goes wrong
Named after the message you will see.
Each of these is a line from the event log or from TradingView, written as it appears — because that is the string you will paste into a search box at the moment you need this page.
The account cannot follow the strategy
The strategy's market and the account's market must agree. A cfd account cannot subscribe to a futures strategy. Check the market on the strategy before assuming the account is the problem.
Right email, wrong server
Email, server and environment together are what identify the login. The same address on another firm's server is a separate login and holds separate accounts — a connection that succeeds and lists nothing you recognise is usually this.
“no subscription” — the alert arrived and nothing traded
The strategy received the signal and no account was following it. Open the strategy, add the account, and re-send. This accounts for more first-run confusion than every other cause put together, because the webhook itself answers perfectly well.
“invalid passphrase” after everything worked yesterday
Somebody pressed New passphrase. The old one stops working immediately and the alert in TradingView still carries it. Copy the current message off the strategy into the alert again.
“rounds to 0 contracts”
Dollar-risk sizing divided your risk budget by the stop distance and got less than one contract, and less than one contract is no trade. A wide stop with a small budget does this every time. It appears in the event log as a rejection rather than as a fill that went missing.
The webhook fires but TradingView reports a failure
Check the three things TradingView itself limits: the receiver has three seconds to answer, only ports 80 and 443 are accepted, and IPv6 is not supported. A hosted endpoint clears all three by construction; a bridge running on your own machine has to clear them itself, on your home connection, while you are asleep.
Questions
Asked before buying, answered either way.
Which prop firms use TradeLocker?
Forex and CFD firms, broadly — TradeLocker is the platform they issue rather than a firm in its own right. If your firm gave you a TradeLocker login with a server name, that is the credential you connect here.
Can one alert trade both my futures and my CFD accounts?
No, and deliberately. A strategy declares one market and only accounts in that market may follow it. Run two strategies if you want both, each with its own alert.
Is a demo server good enough to test with?
Yes, and it is the recommended place to start. Everything described here behaves identically on a demo server, so a malformed alert costs nothing but the lesson.
In the handbook
The reference pages behind the steps above — one thing each, in full.
- Which brokers workThree you can connect today, and what each one asks for.
- Creating a strategyWhat you choose, and the passphrase you only see once.
- A broker login belongs to one Tradeus accountAnd removing the connection does not change that.
Sources
Every claim above about somebody else's product, linked to the page it was read from. If one of them no longer says what this page says, this page is wrong and we want to know: tell us.
Checked against the live product on 14 September 2026. Broker screens and TradingView's own limits change; a step that no longer matches what you see is a step we need to fix.
Next
The neighbouring jobs.
Weighing this against another tool? All 5 compared, every row linked to the page it was read from.
The only step this page cannot do.
Everything above is mechanical and takes about ten minutes. Whether it behaves the way you expect on your own accounts is the part nobody can write down for you.