Keep NinjaTrader® futures history review-ready.
Connect through the shared NinjaTrader® / Tradovate Trade API with read-only access, then sync closed futures trades, fills, fees, and account history into Trader's Second Brain. CSV import remains available for older exports.
- Read-only OAuth sync available
- Demo, prop, and Live accounts
- CSV import available
NinjaTrader® is a registered trademark of NinjaTrader Group, LLC. No NinjaTrader company has any affiliation with the owner, developer, or provider of the products or services described herein, or any interest, ownership or otherwise, in any such product or service, or endorses, recommends or approves any such product or service.
From read-only OAuth to reviewed journal.
Native read-only sync is available now. CSV import remains available for older exports and reconciliation.
-
01
Choose the account environment
In TSB Settings, select NinjaTrader and choose Demo for simulated and supported prop-firm accounts, or Live for a real brokerage account. The two environments remain separate connections.
-
02
Continue through the shared sign-in
NinjaTrader hosts Trade API authorization on a Tradovate-branded page. Sign in with the credentials supplied by the broker or prop firm; seeing Tradovate branding here is expected.
-
03
Approve read-only history access
Approve Account Information, Orders, Positions, and Contract Library. TSB does not request Market Data, trading, funds, alerts, chat, or account-risk permissions.
-
04
Run the first sync
TSB imports available closed-trade history, reconstructs scale-ins, partial exits, and reversals from native fills, and keeps future syncs deduplicated by provider execution identity.
CSV remains useful for history outside the provider reporting window. Use Trade Performance or Executions, and prefer Executions when the fill sequence is needed to verify scale-ins, partial exits, or reversals. Strategy Analyzer results are not live execution history.
History in. No trading access.
OAuth gives TSB read-only access to the account and completed trade history. TSB does not receive the account password and cannot place, change, or cancel orders, move funds, or request a withdrawal.
Read the broker data security model- Current input
- Read-only OAuth sync; optional CSV backfill
- Data scope
- Completed trade and account history
- No trading or money movement
- TSB cannot place or change orders, transfer funds, or request withdrawals.
- Native sync
- Available with read-only OAuth
Questions before you connect or import.
Answers based on the current OAuth sync and supported file imports.
Why does the Tradovate sign-in page open?
NinjaTrader hosts its Trade API OAuth authorization on the shared Tradovate page. This is the expected sign-in flow for the integration.
Should a prop account use Demo or Live?
Choose Demo for simulated and supported prop-firm accounts, including accounts exposed through the provider demo environment. Choose Live only for a real brokerage account in the live environment.
What does sync bring into TSB?
Read-only OAuth brings available completed futures trades and native fills, including account, instrument, side, quantity, price, time, execution identifiers, and available fees or P&L. CSV Trade Performance or Executions is a separate route for older activity.
How much history does the first sync request?
The initial OAuth sync requests up to 30 days of available provider reporting history, then continues incrementally. Provider availability can vary by account; use CSV for older activity that falls outside that window.
How are partial exits and repeated syncs handled?
TSB reconstructs the position lifecycle from native fill identifiers. Scale-ins and partial exits stay in one completed trade, while repeated syncs update the same execution identity instead of inserting another copy.
Which NinjaTrader® export should I use for older history?
Use Trade Performance or Executions. Executions is preferred for scale-ins, partial exits, and reversals because it preserves the fill sequence.
Can TSB place or change orders in NinjaTrader®?
No. OAuth is read-only and TSB does not request order-entry, transfer, withdrawal, or account-risk permissions.
Start with the trades you already have.
Connect the account with read-only access, review the first synced trades, and keep later closed trades attached to the same journal account.