Which Trading Platforms Can a Journal Actually Sync With?

Why "Does It Connect to My Broker?" Is the Only Question That Matters First

Every journal's landing page lists R-multiples, SQN, Monte Carlo, walk-forward analysis. None of that matters if the tool cannot get your trades in. A journal that requires you to hand-type every fill is a spreadsheet with a login screen, and the analytics on top of it are only as good as the data you were willing to type in after a losing day.

So before anything else, the actual question is narrower and more mechanical: what does this tool see, and how did it get access to see it? That question has three different answers depending on your platform, and vendors — ourselves included, historically — are not always precise about which one applies to you.

The Three Connection Types, and What Each One Can and Cannot See

Almost every integration on the market is one of three mechanisms, and they are not interchangeable:

• Broker-side API session. The journal opens a persistent session directly to your account through the broker's own API. It can see open positions and live balance, and it does not depend on a terminal being open. This is the only mechanism that supports real-time drawdown headroom.
• Terminal-side script or EA. A script running inside your trading terminal writes trades out when they close. It sees closed trades only, and only while the terminal is running — if it is closed or a VPS drops, anything that closes in that window can be missed.
• File import (CSV). You export a trade or fill list from your broker or terminal and upload it. It sees everything the export contains, but only after the fact and only when you remember to do it.

Nobody who trades futures needs to be told this in the abstract — 27% of the traders we talked to while researching this piece run on a platform where MetaTrader is simply not part of the picture, and the honest answer for them looks different than it does for a MetaTrader forex trader. The rest of this piece is the platform-by-platform version of that answer.

MetaTrader 4 and 5

SignalDeck connects to MT4 and MT5 through MetaApi, a broker-side session using your login credentials — no Expert Advisor to install, no chart to keep attached. It is an Elite-plan feature and the only integration with real-time account balance sync, which is what feeds live drawdown headroom and balance-aware position sizing. It is worth being precise about what "live" means here: it is a persistent session that syncs trades automatically and refreshes balance and open positions on each connection — not a tick-by-tick feed. For the full mechanics and why the distinction matters in a prop challenge, see our MetaApi vs. EA import breakdown.

Futures Platforms: Tradovate, Rithmic, NinjaTrader

This is where precision matters most, because the three names get used almost interchangeably by traders and almost never mean the same integration.

Tradovate accounts sync directly. NinjaTrader and Rithmic-based setups go through CSV export — NinjaTrader has a named format in SignalDeck's importer with automatic futures contract multiplier resolution so P&L calculates correctly without manual math.

The carve-out that trips people up: many, but not all, Apex and Topstep evaluation accounts run on Tradovate under terms that restrict outside API access. If that is your account, a live connection is not available regardless of the underlying platform, and CSV is the path. The platform name on your login screen is not enough information — check with your specific firm and account type before assuming either way.

Everything Else: cTrader, IBKR, SnapTrade, Indian F&O Brokers, In-House Dealer Terminals

cTrader connects live via OAuth across any cTrader broker — IC Markets, Pepperstone, FP Markets, FxPro, Fusion Markets, and others. Interactive Brokers connects through the free IBKR Flex Web Service, with an end-of-day balance card. SnapTrade is an aggregator covering 30+ brokers across the US, Canada, Europe and Australia — Robinhood, Webull, Schwab, Fidelity, Questrade, Trading 212 and more.

Below that tier is where honesty gets harder, because there is no vendor integration to name. Indian F&O brokers running proprietary dealer terminals, and in-house desk platforms with their own closed accounting stack, have no dedicated connector today. Generic CSV is the answer — not a named preset, just the raw importer with a column mapping step. It works, and it is the same recommendation we would have given ourselves credit for making earlier: we once told an Indian F&O trader that live sync "may not connect" when the accurate answer was simpler — no live sync, full CSV support. Vague hedging cost that conversation. It will not cost this one.

What You Still Get With CSV Only

Say the trade-off out loud instead of burying it in fine print:

All of the quant layer — R-multiples, expectancy, SQN, Monte Carlo — runs on closed-trade history regardless of how it arrived. What CSV genuinely cannot give you is a live number for how much room you have left against a drawdown limit while a position is still open. That gap only closes with a live connection, because it requires reading your account's current state, not its history.

"CSV import will not tell you what you can lose right now. It will tell you, precisely, what you have already survived — and that turns out to be most of what a journal is for."

A Compatibility Checklist Before You Pay for Any Journal

Five questions to ask any vendor — including us — before you commit: