Automate
Send a TradingView alert to a Rithmic account
Rithmic is what most futures prop firms run on, and connecting it asks for two things beyond your username and password: which SYSTEM your account lives on, and which GATEWAY to reach it through. Both come from your firm, not from us, and getting either wrong is the reason most first attempts fail.
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.
- Your Rithmic username and password, plus the system and gateway your prop firm names.
- 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 Rithmic asks for
- Username, password, system, gateway
- Gateways
- 13 regional entry points; Core (Chicago) is the default
- Live system default
- Read-only until order routing is enabled
- What counts as one login
- Username together with the system
Step by step
What to do, in order.
- 1
Pick the right Rithmic system
Rithmic Paper Trading is the one most people need: it is where prop-firm evaluations and funded simulated accounts live. Rithmic 01 is live money. Rithmic Test is Rithmic's own development environment and carries its own gateway, so no gateway choice appears for it. The same username on two systems counts as two separate logins.
- 2
Pick the gateway your firm names
The gateway list is thirteen regional entry points — Chicago, Frankfurt, New York, Sydney and so on — and Core (Chicago) is the default. Pick the one your firm names. A wrong gateway usually fails to log in rather than failing quietly, which is the better of the two failures.
- 3
Check the accounts arrived
You do not add accounts by hand. Once the connection is up, Tradeus asks Rithmic which accounts it holds and lists them underneath. If none appear, nothing downstream can work and there is no point configuring a strategy yet.
- 4
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.
- 5
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.
- 6
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.
- 7
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.
- 8
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.
- 9
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.
A Rithmic 01 connection reads but does not route
A connection to the live system reads balances and positions and does not place orders until order routing is explicitly enabled. That is deliberate: a live account should not begin trading because a webhook was mis-pasted. If a live account is quietly doing nothing, this is usually why.
Same username, wrong system
Your username on Rithmic 01 and the same username on Rithmic Paper Trading are two different logins and are claimed separately. Connecting the wrong one produces a working connection holding accounts you did not mean to trade.
“Session closed” does not pause your strategies
A dropped session means orders have nowhere to go, not that anything stopped. If you have armed locks, a disconnected broker also means an unenforced limit — which is the one case where a silent failure costs more than a loud one.
“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 Rithmic system does a prop firm evaluation use?
Rithmic Paper Trading, in almost every case — that is where evaluations and funded simulated accounts live. Rithmic 01 is live money. If you are not certain, your firm's onboarding page names it; guessing produces a connection that logs in and holds no accounts you recognise.
Which gateway should I choose?
The one your prop firm names. Core (Chicago) is the default and is correct for many US firms, but the list has thirteen entries for a reason. A wrong gateway normally refuses the login outright rather than connecting badly.
Can I connect a live Rithmic account?
Yes, and it starts read-only: balances and positions are read, orders are not routed until routing is explicitly enabled on that connection. It is an extra step on purpose, because the alternative is a live account that starts trading on a mis-pasted URL.
Does connecting Rithmic here stop me using my firm's own platform?
No. The connection reads your accounts and places orders through Rithmic like any other client; your firm's platform keeps working. What it does do is claim that login for your account here — the same Rithmic login cannot be connected under two subscriptions at once.
In the handbook
The reference pages behind the steps above — one thing each, in full.
- Connecting RithmicWhich system to choose, and why the gateway matters.
- 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.
- Accounts and what their status meansFive states, and which of them stop trading.
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.