Tradovate Trade Sync connects one or more independent Tradovate OAuth identities to Journalit. Manage each connection on Journalit.co, then choose provider accounts, history, and vault mappings inside the Obsidian plugin. Journalit records the exact commissions and fees charged by Tradovate for new and historical trades, with no manual commission rules required.
See the Tradovate trading journal overview for sync and CSV import side by side, what is captured, and the limits.
Supported NinjaTrader brokerage accounts that use Tradovate account access use this same authorisation and synchronisation workflow. The connection is approved through Tradovate, then managed and mapped in Journalit exactly as described below.
Use this guide for automatic synchronisation
If you only want to import a Tradovate CSV file, use the Tradovate CSV Export Guide instead. File import and Trade Sync are separate workflows.
Sign in to the same Journalit account on the website and in the Obsidian plugin.
Tradovate connection management and synchronisation require an eligible Journalit plan.
Have access to each Tradovate identity that contains the Demo or Live accounts you want to synchronise.
You can map to existing local accounts or create suitable accounts during plugin setup.
The setup uses both Journalit.co and the Obsidian plugin.
Create and manage independent Tradovate OAuth connections, including pause, resume, reauthorisation, disconnect, and connection-scoped cloud-data deletion.
Select provider accounts under each connection, choose initial history, map vault accounts, start synchronisation, and write trade notes.
Sign in to Journalit.co and open Dashboard → Integrations. Choose Connect another Tradovate account. Journalit creates a separate connection with a safe label such as Tradovate 1.
Approve the connection in Tradovate. When Tradovate returns you to Journalit, the website confirms whether the connection succeeded.
After approval, the website shows the result on the matching connection card and directs you back to Journalit in Obsidian. The remaining setup belongs to the vault, so it is completed in the plugin.
Open Settings → Account & Sync → Trade Sync in Journalit and find the Tradovate provider card. Each OAuth connection has its own provider-account list and synchronisation controls.
Journalit loads the available Demo and Live accounts. If one environment could not be checked, retry discovery before assuming the account is unavailable.
Choose the Tradovate accounts that should feed this vault. Journalit keeps Demo and Live accounts separate even when their display names are similar. If the same canonical account is visible through two OAuth identities, only one connection can have synchronisation enabled for it at a time.
Select one history option for each enabled account:
All available means the history Tradovate currently exposes for that account. Journalit resolves that provider window and is not a guarantee of complete account-lifetime history or of every trade since the account was opened. It is also not limited to activity collected only after you connect.
The history boundary limits older closed trades. Existing open positions are still synchronised so Journalit can track their current lifecycle.
Choose an explicit local Journalit account for every enabled Tradovate account. Create a local account if no suitable one exists. Journalit does not silently fall back to the first account in the vault.
Use Sync Tradovate to this vault. The plugin starts the broker synchronisation, waits for it to finish, and writes the resulting trade notes into the vault.
A Tradovate account can move to a different local Journalit account after notes already exist. Journalit asks how to handle the existing notes:
Use the new Journalit account for future updates and rewrite eligible existing trade notes to use it.
Save the new assignment without rewriting existing notes immediately. A later broker update to an existing trade can still use the new assignment.
Locally deleted notes and conflicting local changes stay unchanged. Pending note updates can be retried with another synchronisation.
Journalit can continue checking Tradovate activity even when the vault is not open.
When the plugin starts or reconnects, it brings in trades that were added or updated while you were away.
A position can move from open to partially closed to closed without creating separate trade notes.
Journalit records Tradovate's commission, exchange, clearing, and NFA fees for new and historical trades.
Broker updates do not replace your thesis, notes, tags, screenshots, reviews, or custom fields.
Journalit records gross P&L when a trade closes, then adds the exact commission and fees charged by Tradovate. This applies to new trades and to the history collected when you first connect an account.
| What | When | Where it comes from |
|---|---|---|
| Trade and gross P&L | About 5 minutes after you close | Live Tradovate connection |
| Commission, fees and net P&L | Usually within minutes of closing | Tradovate's live fee feed |
| Confirmation | The next day | Tradovate's official daily statement |
Return to Dashboard → Integrations on Journalit.co for connection lifecycle actions. Every action applies only to the card where it is started.
Stop new scheduled synchronisation without removing the connection or existing trade data.
Allow scheduled synchronisation to continue after a pause.
Refresh one existing connection when its authorization expires or stops working, without resetting plugin account configuration.
Stop future synchronisation while preserving existing synced trades and Obsidian notes.
Remove provenance owned by the selected connection after reviewing its deletion-impact summary. Shared canonical trades survive while another source still owns them. Local Obsidian notes are untouched.
Disconnect and delete are not the same
Disconnect preserves cloud trades. Delete cloud data is a separate destructive action scoped to one connection. A shared canonical trade is preserved when another connection or source still contributes it.
The website keeps each healthy card concise: safe connection label, status, last successful sync, and next scheduled sync. Busy states, errors, notices, deletion progress, and job polling stay on the owning card.
When Journalit detects a problem, the page shows the relevant recovery actions. Use Email support to prepare a message with the error details, or choose Ask on Discord for community help.
Compare providers and understand the shared synchronisation model.
Set up the FTP-based MT4 workflow.
Use the separate file-based Trade Import workflow.
What Tradovate support includes, in one place: sync, import, captured data, and limitations.
How supported NinjaTrader brokerage accounts journal through Tradovate account access.
Organise the local accounts that receive synchronised trades.
Read more about how Journalit handles account and service data.
