DXtrade is where a growing number of forex prop firms route their evaluations, and it’s also where your trade data goes to hide. The platform records everything and exposes almost none of it to outside tools — so the journal you need has to be built from what you can export, not what an API will hand you.
The good news: DXtrade’s exports are complete enough to reconstruct a real journal, once you know the workflow.
Why DXtrade Prop Platforms Limit Direct Connections
DXtrade is a white-label platform — Devexperts licenses it to brokers and prop firms, who each run their own locked-down instance. That architecture is exactly why direct connections are hard:
- The API is gated per deployment. DXtrade has a REST and streaming API, but access is controlled by the firm that runs the instance. Most prop firms don’t hand out API keys to retail accounts, so a tool can’t just log in and pull your fills.
- Every firm’s instance is slightly different. Symbol naming, timezone, and export column order can vary between one firm’s DXtrade and another’s, so there’s no single universal connector.
The practical consequence: for the vast majority of DXtrade prop accounts, file export is the reliable path, not a live API link. That’s not a dead end — it just means the journal is import-driven rather than streaming, and you build a small repeatable routine around it.
CSV Export and Statement Import Workflow
DXtrade gives you the data in two forms, and it’s worth grabbing both.
- Positions/History grid export. In the DXtrade web terminal, open the closed-positions or history view and export to CSV. This is your primary feed — one row per closed position, with entry, exit, size, and P&L.
- Account statement. The periodic statement is the reconciliation backstop: it carries the account-level totals you’ll check your imported P&L against, so nothing silently goes missing.
The workflow is simple and repeatable: export the history CSV for the period, import it into the journal, then reconcile the imported net P&L against the statement total. Do the export on a fixed cadence — end of each session or end of week — and the record stays current without ever retyping a trade the way you would in a spreadsheet, where one mistyped fill quietly poisons every stat downstream.
Normalizing DXtrade Fields Into Structured Trades
A raw DXtrade CSV isn’t a journal yet — it’s broker-shaped columns. The import step maps those into the fields analytics actually run on.
| DXtrade export field | Structured trade field | Why it needs handling |
|---|---|---|
Symbol (e.g. EUR/USD) | Instrument | Firm-specific naming may need normalizing |
| Side / Buy-Sell | Direction | Drives long vs short stats |
| Quantity / Lots | Position size | Lots must map to units for R math |
| Open & Close price | Entry / exit | The basis for every price-derived metric |
| Open & Close time | Timestamps | Often need timezone alignment to your session |
| Realized P&L | Net result | Confirm it’s net of commission and swap |
The two fields that trip people up are time and P&L. DXtrade instances often report in a server timezone that isn’t yours, so a trade taken at your 9:30 open can show as a different hour — align it, or your session-based analysis lies to you. And confirm whether the P&L column is gross or net of swap and commission before you trust an expectancy number built on it. A tool like Shibiki handles this normalization on import through auto-journaling, reconstructing structured trades from the export so you’re not hand-cleaning columns every session — the same job a dedicated journal like Tradezella does, with edge health computed on top.
Tagging by Strategy for Edge Tracking
Once trades are structured, the payoff is attribution — tagging each trade to the setup that produced it. DXtrade won’t do this for you (it doesn’t know your strategies), so it’s a tag you add on import or shortly after.
This is what turns a pile of fills into decisions. Group your London-breakout trades separately from your news fades, and each accumulates its own sample — its own win rate, its own expectancy. Suddenly you can see that the setup that feels best is the one bleeding, and the boring one is carrying the account. On a firm like The Funded Trader, where the evaluation punishes an unprofitable setup you keep trading on feel, that per-strategy view is the difference between passing and paying another fee. Shibiki wraps each strategy’s expectancy in a Wilson confidence interval, so a setup that’s up over a handful of trades is flagged as unproven rather than mistaken for a real edge.
Keeping the Journal Current With a Repeatable Import
The failure mode of any import-driven journal is falling behind — you skip the export for a week, then face a backlog you never clear, and the record rots. Beat it by making the import a fixed, tiny ritual rather than an occasional project.
- Pick a cadence and hold it — end of each trading day is ideal, end of week is the minimum.
- Export the same views the same way every time, so the columns line up and the import is boring.
- Reconcile against the statement each time: trade count and net P&L should match, and if they don’t you fix it while it’s one session, not one month.
Kept current, a DXtrade journal built this way is every bit as analytical as one fed by a live API — the data just arrives in batches instead of a stream. And because the record is complete and honest, the edge stats you review before your next session are the real ones, not the flattering version your memory would supply.
Related: Trade journal vs spreadsheet · Trading expectancy, explained · Shibiki vs Tradezella