Tradovate uses OAuth: Tradeus sends you to Tradovate, you log in there, and the token that comes back is stored encrypted against your connection. There is no password field, and nothing to rotate here when you change your Tradovate password.
If you picked a prop firm on the connect screen first, the firm travels through Tradovate's sign-in and the connection comes back filed under it. Re-authorize on Broker setup leaves the firm as it is.
Sign out between two firms' logins
Tradovate's consent screen uses whichever Tradovate login your browser is still signed in to, and does not ask. So before you connect a second firm's login, sign out at trader.tradovate.com. Skip it and Tradovate hands back the first login again — and if that one is already connected here, no second connection appears: the existing one is filed under the firm you just picked instead.
Edit firm on Broker setup puts it back; then sign out and connect the second login. See Connect a prop firm account.Tradovate runs two separate deployments, and neither can see the other's accounts. Prop firm and evaluation money is simulated and lives on one; money you funded yourself lives on the other. You are not asked which you have — after you approve, Tradeus looks on both.
What comes back
Accounts on one side
One connection, marked
Demo or Live. That mark is the difference between simulated prop firm money and real cash, so it is not cosmetic. One exception: a live account that first appeared under your Demo connection stays marked Demo.Accounts on both
Two connections, one of each. Tradovate treats them as different logins and so does Tradeus.
Accounts on neither
Nothing is stored, and the message says what each side answered — but only once both really answered. Usually the login was a personal one and the prop firm issued its own.
Firms on their own servers
NinjaTrader, which runs Tradovate, is moving prop firms onto servers of their own — Lucid among them since October 2026. Tradovate tells Tradeus where your firm's server is, and Tradeus goes there: nothing to set, and a connection follows its firm if it moves while you are connected. Should a firm ever move somewhere Tradovate does not vouch for, Tradeus does not send your authorization there; we are told at once, and at worst you press
Re-authorize once.Tradovate not answering
Tradovate has maintenance windows — daily 4–5 pm CT, Fridays until 8 pm CT, and Saturday night to Sunday morning — and around them it can answer oddly for a while. Tradeus asks again a few seconds later; if Tradovate still is not answering normally, your authorization is kept and Broker setup shows
Waiting for Tradovate. Tradeus keeps asking and connects the accounts by itself as soon as Tradovate answers — nothing to do. It stops after 48 hours, or sooner if Tradovate is down entirely for longer than an authorization lives (about 90 minutes), and says so in your Logs — connect again then. If Tradovate lists the accounts but will not open the session yet, the same happens: kept, and tried again.Prop-firm logins
Each connection is matched to the accounts Tradovate lists for your own login, never to the firm that owns them. On a prop firm's Tradovate every trader's accounts are their own, so traders at the same firm never block each other. An account can belong to one Tradeus account only: one that is already connected to a different Tradeus account is left out, and if every account on the login is, you are told so and nothing is connected.
Authorization expires
A Tradovate access token lives about 90 minutes and Tradovate issues no refresh token, so Tradeus renews it from the token it already holds while the connection is open. It lapses two ways: the connection stays closed for longer than a token lives, or those renewals cannot reach Tradovate for long enough — a broker outage, which is not something you did. Either way the connection shows
Authorization expired with a Re-authorize button, and nothing routes while it says that.Tradovate limits how often each login is asked
Tradovate allows each login 5,000 requests an hour, counted across every account on it and every app connected to it. Tradeus asks once per login where Tradovate answers for all of its accounts, lets a dashboard show a reading a few seconds old, and has the account lock read Tradovate accounts every ten seconds — a fill still reaches the lock at once. If Tradovate says a login has asked too often anyway, the connection stays open and orders still go out; Tradeus stops the background reads for a minute or more so the limit can clear, and the account lock says it cannot measure until then. Other tools connected to the same Tradovate login count against the same 5,000.