Copy trades on Tradovate: connect your login
Tradovate is the shortest connection form in MirrorFill: a username and a password. No API keys, no environment picker, no add-ons. Under the two fields sits a Connect with Tradovate button, the passwordless route, which is built but not switched on yet (see the last section). Once the login passes Test, its accounts appear in the Copy Rules pickers and can lead or follow like any other account.
Steps
- Open Accounts and click Add connection. Name the connection.
- Pick the Tradovate tile in the platform picker.
- Enter your Tradovate username and password, the same ones you sign in to Tradovate with. Those two fields are all you have to fill in. Below them you will see a divider reading "Or connect without a password" and a Connect with Tradovate button; leave it alone for now, and read the last section for what it does.
- Press Test, then Add connection. A working login answers "Connected. N accounts found:" with your account ids.
Demo vs live is detected for you
There is no demo/live picker. Test works out which environment the login belongs to and writes the answer on the connection. The Details column on the Accounts page then reads Demo account or Live account. If that ever changes on Tradovate's side, the next Test updates it. There is nothing to configure and nothing to re-do if you guessed wrong, because you never guess.
The "Connect with Tradovate" button
Under the password fields, after a divider reading "Or connect without a password", there is a Connect with Tradovate button and a line explaining that it sends you to Tradovate's own website to authorize the connection. That is the OAuth route, and it is deliberately visible before it works.
On this deployment it is not switched on yet: it needs a registration with Tradovate that is not in place. Press it and it answers, in place, "Tradovate OAuth isn't enabled on this deployment yet - username and password works today." Nothing is saved and nothing breaks. The username and password above it are the working path.
When the registration does land, the button saves the connection first (the authorization has to attach to a row) and then hands you to Tradovate to approve it. A connection authorized that way reads OAuth - Demo account or OAuth - Live account in the Details column on the Accounts page, and because Tradovate's tokens are short-lived, an expired one shows an amber Reauthorize link right beside it.
One session per login
Tradovate allows one API session per login. So if the copier is running with this login, Test refuses instead of kicking the copier off: the answer is an explicit "copier is running on this Tradovate login: stop it before probing". The fix is exactly that: stop the copier from the engine command strip, run your Test, then start copying again.
If your connection drops at odd moments even though the credentials pass Test, another program is probably taking the session. Work through Tradovate session conflicts.
Quick answers
Do I need Tradovate's API Access add-on?
No. MirrorFill connects with the username and password you already have. There is nothing extra to buy from Tradovate.
Can I sign in with OAuth?
Not yet, though the button is already on screen. Connect with Tradovate sits under the password fields in the Add connection dialog, and pressing it today answers "Tradovate OAuth isn't enabled on this deployment yet - username and password works today." The flow behind it is built and waiting on a registration with Tradovate. Once that is in place, the same button sends you to Tradovate's own website to authorize the connection instead of typing a password here.
Did it connect to my demo or my live account?
Check the Details column on the Accounts page. It reads Demo account or Live account after the first passing Test.