Trading journal that syncs with Tradovate and ProjectX

The direct answer

QuantLab Journal syncs Tradovate through OAuth and ProjectX through a username and API key. The two connections have different refresh behavior, so treat them as separate workflows. The prop firm trading journal guide places both in the full account review.

Topstep is supported through ProjectX. QuantLab does not use the name of a prop firm as proof that every account from that firm is exposed through a particular provider.

Tradovate connection

The OAuth flow stores an access token and its expiry. You can add more than one Tradovate connection, discover accounts, select the ones you want, and sync account history. The sync is initiated by you rather than described as continuous background polling.

After the first sync, compare a narrow period with Tradovate. Verify contracts, quantities, fill prices, and results. Keep Tradovate as the source for official account information.

ProjectX connection

Enter the ProjectX username and API key. QuantLab validates those credentials, stores them encrypted, and lets you import selected accounts. You can trigger a manual sync. The connection can refresh in the background when the last sync is more than 30 minutes old.

If an account does not appear, do not substitute a similarly named account. Confirm which provider exposes the account, then use CSV import if the supported connection does not apply.

One review after both imports

Create separate prop accounts with their own targets and drawdown settings. QuantLab also stores drawdown already used and a consistency limit. It calculates maximum drawdown and evaluates the configured consistency rule for the recorded trades.

Reconcile each provider independently before comparing behavior across accounts. A missing execution in one source can create a false difference. QuantLab's behavior detectors and replay tools become useful only after the underlying records agree with the broker statements.

The journal is free during beta. Signup currently requires an approved waitlist email.

Diagnose a stale connection

When recent trades are absent, first confirm the selected provider and account. Check the last sync time before reconnecting credentials. For ProjectX, a manual sync gives you a direct test. For Tradovate, initiate a new sync and compare the returned history with the source.

Avoid uploading the same executions through a connection and CSV until you understand the missing range. CSV duplicate protection applies to file imports, but mixed sources still deserve an account-level reconciliation. Record the date boundary you checked so a later review can distinguish an old gap from a new one.

Choose one source for each range

Document which connection or file supplied each period. If you change import methods, use a clean date boundary and compare the handoff day. This reduces the chance that overlapping sources create a confusing result.

After the import agrees, check the configured prop account settings separately. A working broker connection supplies executions. It does not select the correct profit target, drawdown, or consistency limit for you.