Supported Brokers & Platforms

MimikTrader copies trades by talking directly to your broker's API — not by watching your screen or simulating keystrokes. That means the list of brokers you can use is defined by which broker integrations MimikTrader has built, not by which trading platform you personally click around in. This article covers what's supported today and a distinction that trips people up: the difference between a connection and an account.

Tradovate — Connect with OAuth

Tradovate is MimikTrader's primary, fully-supported broker integration. You connect using Tradovate's own OAuth authorization — you log in on Tradovate's page, approve the permissions MimikTrader is requesting, and Tradovate hands back a revocable access token. MimikTrader never sees or stores your Tradovate password.

Once a Tradovate login is authorized, MimikTrader automatically discovers every trading account under that login — live accounts, demo/simulation accounts, and prop firm evaluation or funded accounts all show up without any extra steps. For the full walkthrough, see How to Connect Your Tradovate Account.

NinjaTrader — via Your Tradovate-Brokered Account

MimikTrader does not have a separate, standalone NinjaTrader integration. If your prop firm or broker gives you a NinjaTrader account that is actually cleared and brokered through Tradovate behind the scenes, you connect it the same way as any other Tradovate account: using your Tradovate OAuth credentials. Once connected, it behaves exactly like a normal Tradovate account — because to MimikTrader, and to Tradovate's own API, it is one.

The details on what this means, what to check before you connect, and how orders placed from NinjaTrader itself (or from TradingView pointed at that account) fit into the picture are covered in Using NinjaTrader Accounts with MimikTrader.

ProjectX — Connect with Your Username and API Key

ProjectX is supported as a broker connection. You connect it with your ProjectX username and API key, rather than the OAuth redirect flow used for Tradovate. Generate an API key from your ProjectX account and use it, together with your ProjectX username, to authorize the connection.

Behind a ProjectX connection sits your specific prop firm's ProjectX environment — this routing is handled automatically once your connection is set up, so you don't need to hunt for a firm-specific server address or gateway URL yourself.

Rithmic — Connect with Your Username and Password

Rithmic is supported as a broker connection. Rithmic is the order routing infrastructure behind a large share of futures prop firms, so if your firm hands you Rithmic credentials rather than a Tradovate or ProjectX login, this is the connection you want.

When you add the connection you pick your firm's Rithmic system from a list — Topstep, Apex Trader Funding, Bulenox, Tradeify, Lucid Trading and others are all there, along with Rithmic 01 and Rithmic Paper Trading for retail accounts. Then you enter the Rithmic username and password your firm issued you. Choosing the system is what tells MimikTrader which Rithmic gateway your accounts live behind, so you don't need to find a server address yourself.

What "Connection" vs. "Account" Means

These two words mean different things in MimikTrader, and mixing them up is the most common source of confusion when setting things up:

• A connection is a single authorized link to a broker login — one Tradovate OAuth authorization, one ProjectX username/API-key pair, or one Rithmic username/password. You create one connection per broker login you have.
• An account is an individual trading account underneath a connection — a specific balance, a specific account number. A single connection can, and usually does, cover multiple accounts. For example, one Tradovate login might have a personal live account, a demo account, and two prop firm evaluation accounts all under it — that's four accounts surfaced through one connection.

In practice this means you don't need to "connect" separately for every funded account a prop firm gives you, as long as those accounts share the same broker login. One connection covers everything underneath it. If you have accounts spread across multiple different logins (say, two separate prop firms that each issued you a distinct Tradovate login), you'll need one connection per login — see Connecting Multiple Logins in the Tradovate connect guide for that scenario.

If Something Isn't Connecting

If a connection won't authorize, an account won't show up after you connect, or a previously working connection starts showing an error, that's a troubleshooting question rather than a "which broker" one — head to Troubleshooting Connection Issues for status-indicator meanings and fixes, or Reconnect, Reauthorize & Remove Accounts for what the connection states mean and how to safely disconnect or reauthorize.