Bring your trades in
Everything in TraderLeveling runs on your real trades, so this is the step that makes the app light up. Two ways in: connect a platform (it imports for you) or import a CSV from anywhere. Both live under Settings → Data & Integrations.
Read-only, encrypted, can't trade.Platform credentials are encrypted before they're stored and are only ever used server-side to read your fills. Nothing here can place a trade or move funds, and Interactive Brokers connects via a report-only token, never your IBKR login. Disconnecting removes the stored credentials.
Tradovate
TV
Tradovate
Futures broker, also the platform behind many prop-firm evals
Generate an API key in Tradovate
In the Tradovate platform, open Settings → API Access and create an API key. You'll get a Client ID (a short number, e.g.
4523) and a secret.Connect in TraderLeveling
Go to Settings → Data & Integrations, hit Connect on Tradovate, and fill in: environment (Live or Demo/Sim), your Tradovate username and password, the Client ID, and the secret.
Connect & test
The app verifies the credentials and pulls your fills immediately. Fills are paired into round-trip trades automatically.
Heads up: the Client ID is the number Tradovate shows with your API key, not your username. If you trade a prop-firm eval that runs on Tradovate, connect with the Tradovate credentials that firm gave you.
Topstep (TopstepX) & ProjectX prop firms
PX
ProjectX
The platform behind TopstepX and many prop-firm dashboards
Generate an API key at your firm
In your firm's ProjectX dashboard, create an API key, on TopstepX that's Settings → API. The key grants data access only.
Connect in TraderLeveling
Under Settings → Data & Integrations, choose your firm from the list (Topstep, The Futures Desk, …), then enter your platform username and the API key.
Firm not in the list?
Pick Other ProjectX firm… and enter the firm's gateway slug, the
<slug> in api.<slug>.projectx.com. Your firm's support can tell you its gateway name.Interactive Brokers (Flex Query)
IB
Interactive Brokers
Read-only by design, a Flex token, never your IBKR login
Create a Flex Query
In IBKR Account Management, go to Reports → Flex Queries and create a new query with Trades → Executions selected and the format set to XML. Note the Query ID (e.g.
912345).Enable the Flex Web Service
Under Settings → Account Reporting, enable the Flex Web Service and copy the token it gives you. The token can only fetch reports, it cannot trade or move funds.
Connect in TraderLeveling
Under Settings → Data & Integrations, hit Connect on Interactive Brokers and paste the token and Query ID.
CSV import: any platform
No direct connection for your platform? Every broker exports CSV, and TraderLeveling reads two shapes automatically, detected from the headers, no template to fill out:
- Closed-trade exports, one row per finished trade. Columns like symbol, side, entry/exit, P&L; optional extras like risk, setup, and notes come along for the ride.
- Raw fills / executions exports, the order-by-order logs that Tradovate, NinjaTrader, and ProjectX platforms produce. Fills are paired into round-trip trades for you.
Import from Settings → Data & Integrations. Dollar signs, commas, parenthesized negatives, and US dates are all normalized, export and upload, don't massage the file first.
Safe to re-import.Imports are idempotent, uploading the same file (or an overlapping export) again never duplicates trades. Files up to 10 MB.
After the import
- Imported trades land in your Trade Log and on The Tape, ungraded, grading happens when you tag a setup and review them. That's by design: the grade should come from your rules, not the import.
- Connected platforms import on demand with Sync now; background auto-sync is coming.
- Numbers look off? Check the account filter first, multi-account imports (prop firms especially) file trades per account.
Troubleshooting
- Tradovate: "Client ID should be numeric", you've entered your username in the cid field; use the number from Settings → API Access.
- ProjectX: connection fails on "Other", the gateway slug is wrong. Confirm the exact
api.<slug>.projectx.comname with your firm. - IBKR: "rejected the request", re-check the token and Query ID, and make sure the query is a Trades → Executions Flex Query in XML format. Brand-new tokens can take a few minutes to go live.
- CSV: rows skipped, the importer skips rows it can't read rather than failing the file; the import summary says how many. If a whole file is rejected, the headers likely match neither shape, email it to support@traderleveling.comand we'll add it.