Automate
Send a TradingView alert to a Tradovate account
Tradovate does not accept a TradingView alert directly. Something has to sit between the two: receive the webhook, read the alert, decide the size and place the order on the right account. Tradeus is that something, hosted, so there is nothing to install and nothing of yours has to be awake at 3am.
Checked against Tradeus on 14 September 2026.
Before you start
- A TradingView account with 2-factor authentication enabled — TradingView does not allow webhook alerts without it.
- A Tradovate login. Prop-firm evaluation and funded accounts count; you do not need a separate personal one.
- A Tradeus plan that includes the TradingView webhook — Algo or Unlimited. The Manual plan has no webhook endpoint at all and turns the alert away at the door.
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 Tradovate asks for
- Nothing — OAuth, no password stored
- Webhook URL form
- …/hook/<strategy-id>
- Passphrase
- Shown once, regenerable, invalidates the old one instantly
- Target accounts per plan
- Not counted on any plan
Step by step
What to do, in order.
- 1
Connect Tradovate with OAuth
Tradovate uses OAuth, so there is no password field: Tradeus sends you to Tradovate, you log in there, and the token that comes back is stored encrypted against the connection. Nothing to rotate here when you change your Tradovate password, and nothing to choose — Tradovate runs two separate deployments that cannot see each other's accounts, and after you approve, both are checked.
- 2
Check which accounts came back
Your accounts appear underneath the connection by themselves, each marked Demo or Live. That mark is the difference between simulated prop-firm money and real cash, so it is not cosmetic. If accounts appear on both deployments you get two connections, one of each, because Tradovate treats them as two different logins. If none appear, the message names what each side answered — usually the login was a personal one and the prop firm issued its own.
- 3
Create a strategy and copy its webhook URL
A strategy is the endpoint a TradingView alert posts to, and creating one hands you a URL of the form …/hook/<strategy-id> together with a passphrase. The passphrase is shown once and is never displayed again — put it somewhere before you close the dialog. If it is lost, New passphrase issues another and the old one stops working the same second, so every alert still carrying it starts failing with an unauthorized error.
- 4
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.
- 5
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.
- 6
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.
- 7
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.
- 8
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.
“Authorization expired”
OAuth tokens do not last forever. When one lapses the connection says Authorization expired and offers Re-authorize, and nothing routes while it says that. This is the Tradovate failure that looks like a broken strategy and is not — the strategy is fine, the door is shut.
The accounts you expected are not there
Tradovate's two deployments hold different accounts and neither can see the other's. Prop-firm and evaluation money is simulated and lives on one; money you funded yourself lives on the other. Connecting with a personal login will not surface the accounts your firm issued.
“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.
Can TradingView send orders to Tradovate directly?
No. A TradingView alert can post a webhook to any URL, but Tradovate does not publish an endpoint that accepts one, and the alert carries no authentication of its own. Something has to receive the webhook, authenticate against Tradovate on your behalf and place the order.
Do I need a paid TradingView plan?
You need an account with 2-factor authentication enabled, which TradingView requires for webhook alerts. Webhook availability by subscription tier is TradingView's to state and changes; check it on their own pricing page rather than taking a number from a third-party guide.
Does it work with a prop firm's Tradovate account?
Mechanically, yes: a funded or evaluation Tradovate login connects exactly like any other, and the accounts it holds appear the same way. Whether your firm permits automated order entry is set by that firm's rules and sometimes differs per account — read your own account's terms before you connect it.
How many Tradovate accounts can follow one alert?
As many as you hold. Broker connections and target accounts are not counted on any plan, so one funded account or eight costs the same. What the plans separate is how many strategies and copy groups you may run.
In the handbook
The reference pages behind the steps above — one thing each, in full.
- Connecting TradovateOAuth, and nothing to choose.
- Creating a strategyWhat you choose, and the passphrase you only see once.
- The TradingView alertThe exact message body, field by field.
- When a signal does not tradeRead the event log first — it names the reason.
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.