Guide / Trading 212

How to export your Trading 212 history.

Trading 212 gives you two ways to get your history out: an API key, which lets a tracker read the whole history directly with no file at all, and the CSV export, which covers at most a year per file. This guide walks through both, says which permissions to give a key, and explains what each route can and cannot see.

The short version

API key: ☰ → Settings → API (Beta) → Generate API key

Tick only the read permissions, which are account data, portfolio and history, and copy both the key and the secret. The secret is shown once. No export, no date ranges, and the history stays up to date by itself.

CSV: ☰ → History → Export

Pick a period of up to twelve months, tick orders, dividends, transactions and interest, and export. For a longer history, repeat once per year.

Which route to use

Read-only API keyCSV export
Full historyYes, in one go.One file per twelve months.
Staying up to dateAutomatic.Export and upload again.
Stock splits and corporate actionsRecognised.Not read yet in Parallax (see limits).
AccountsInvest and Stocks ISA. Not SIPP.Any account with a History screen.
What you hand overA key you can restrict and revoke.A file.

If you are comfortable creating a key, it is the better route: it sees your whole history and keeps it current without you remembering to export. If you would rather not issue any credential, the CSV route takes the same history, one year at a time.

Route 1: a read-only API key

  1. Open the menu. In the Trading 212 app or on the website, tap ☰, then Settings, then API (Beta). It appears on Invest and Stocks ISA accounts; switch to the account you want first.
  2. Choose Generate API key and give it a name you will recognise later, such as “Parallax”.
  3. Tick only the read permissions: account data, portfolio and history. Leave order placement unticked. A portfolio tracker has no reason to place or cancel orders, and a key that cannot do it is one less thing to worry about if it ever leaks.
  4. Leave IP restriction off, unless you are restricting it to the tracker’s own server addresses. The key is used by the tracker’s server, not your phone, so a key pinned to your home connection is refused.
  5. Copy the API key and the API secret. The secret is shown once, like a password; if you lose it, delete the key and generate a new one.
  6. Paste both into the tracker. You can revoke the key in the same Trading 212 screen at any time, which cuts off access immediately.

Trading 212 lets each account make only six history requests a minute, so the first import of a busy account takes several minutes, not seconds. It is still working, within Trading 212’s limit.

The API reports every value in the account’s main currency, so multi-currency balances are not available through it.

Route 2: the CSV export

  1. Open History. Tap ☰, then History.
  2. Tap the export button.
  3. Pick the period. Trading 212 currently allows up to twelve months per export. Start with the year you opened the account.
  4. Tick the data: orders, dividends, transactions (deposits, withdrawals and currency conversions) and interest. Leaving transactions out removes the deposits, and without them returns cannot be separated from money you added.
  5. Export. The CSV downloads to your device.
  6. Repeat for every year up to today, with no gaps between the periods.

Upload the files oldest first, one at a time. A tracker that builds your positions year by year needs each year’s starting point before it can read the next one; a file that starts earlier than what is already imported may not be read in full.

Parallax skips every day up to and including the last one it already holds, so the files can overlap by a day or two. The catch is the day you export: if you export in the middle of a day on which you traded, and then trade again, the next upload treats that day as done and skips the later trades. End each export on a day after your last trade, or on yesterday.

Limits of the CSV route in Parallax

Parallax reads the Trading 212 CSV in beta. It was built from a published sample export rather than a real account, so check the import preview carefully the first time. Specifically:

  • Stock splits and other corporate actions are not read yet. Those rows appear in the preview’s skipped list, and a holding that split will show the wrong share count. The API route does not have this gap.
  • Dividend withholding tax is not subtracted separately. Trading 212 states it in the security’s currency, not the account’s, so the dividend is taken as the cash that actually arrived.
  • Times are read as UTC, which matches the API. If a trade near midnight lands on the wrong day, that is why.

What is inside the CSV

Each row has an Action, a time, the instrument’s ISIN, ticker and name, the quantity and price, the exchange rate used, the total in your account’s currency, and a row ID. The Action says what happened.

ActionWhat it isIs it money in or out of the account?
Market buy, Limit buy, Stop buyA purchase.No. Cash became shares.
Market sell, Limit sell, Stop sellA sale.No. Shares became cash.
Dividend (…)A dividend paid, net of withholding tax.No. It is part of your return.
DepositMoney you paid in.Yes, in.
WithdrawalMoney you took out.Yes, out.
Card debitSpending on the Trading 212 card from the account’s cash.Yes, out. It left the account.
Interest on cash, Lending interestInterest paid on uninvested cash, or for shares lent out.No. Part of the return.
Currency conversion feeThe FX fee on a trade in another currency.No. A cost that reduces the return.
Stock split open / close, Stock distributionA corporate action changing how many shares you hold.No money moves. Not read by the CSV route yet.

The Total column is what your account was actually debited or credited after Trading 212’s own currency conversion, which is why it is a better record of cash than quantity times price.

Common problems

The export will not go further back than a year

That is Trading 212’s limit per file. Export one year at a time, or use an API key, which has no such limit.

There is no API (Beta) option in Settings

It appears on Invest and Stocks ISA accounts only. Switch to one of those, or use the CSV export.

The key is refused

Most often a permission was left unticked, or the key was restricted to an IP address that is not the tracker’s. The tracker needs account data, portfolio and history. Delete it and generate a new one without the restriction.

The first import is slow

Six history requests a minute. A few years of active trading takes several minutes; let it finish.

A holding shows the wrong number of shares

On the CSV route, a stock split is the likely cause. Check the preview’s skipped rows, or switch that account to an API key.

Using it in Parallax

Parallax takes either route, one per account: connect a key, or upload CSVs, but not both into the same account. With a key it reads every fill with Trading 212’s own identifier, so repeated syncs never duplicate a trade, along with deposits, withdrawals, fees, interest and corporate actions. Its Trading 212 client issues nothing but read requests, a test fails if that ever changes, and the key and secret are stored encrypted and never shown back to the browser.

Then it rebuilds the history into snapshots and shows whether each move beat keeping what you had. The details are on the coverage page and the security page; how moves and returns are measured is on the methodology page.

Request beta access

Parallax Investing is not affiliated with or endorsed by Trading 212. Trading 212 is a trademark of its owner. These steps were checked against Trading 212’s help centre in September 2026 and can change without notice. This guide is for information and is not investment or tax advice.