<aside> 💡 Only available for Trading212 Invest and UK ISA accounts at the moment.

When retrieving account balances, buyer_power is always equal to cash.

</aside>

<aside> ℹ️ Trading212 allows users to create API keys with granular permissions. If a user connects with a key that doesn’t have all the permissions, some SnapTrade API endpoints may return a 403 to indicate the lack of permissions.

</aside>

Transactions

Fetching transactions uses the “CSV Export” feature in Trading212’s API, which may generate notifications for users that a CSV export is ready for download. On the first account sync, there could be several of these notifications generated as we attempt to fetch the full account history, and after that ~1 per day as we do our regular sync. Note that the user does not need to download or act on these CSVs, SnapTrade imports them automatically with no user intervention required.

The initial transaction sync may take a few minutes due to Trading212’s rate limits.

General information and caveats

<aside> 💡 Only available for Trading212 Invest accounts at the moment.

When retrieving account balances, buyer_power is always equal to cash.

</aside>

Notional (value) orders

In some instances, Trading212 doesn’t directly return the quantity purchased for some orders, while also mixing currencies (eg: account is in GBP, but purchased $2 of US stock). In those cases, these orders will not have a quantity set.

In other cases, Trading212 doesn’t directly return the quantity, but the currencies match (eg: account is in GBP and purchased LSE stock), so we attempt to provide an estimate of the quantity, usually accurate to 1/100th of a percent (<0.01% difference).

Further information on API Keys

<aside> ℹ️ Trading212 allows users to create API keys with granular permissions. If a user connects with a key that doesn’t have all the permissions, some SnapTrade API endpoints may return a 403 to indicate the lack of permissions.

</aside>

API Key permissions

When generating the key on the Trading212 website, the user needs to preferably select all permissions - the only exception being “Orders - Execute”:

• for a read-only connection it should not be selected
• for a trading connection it is required in order for trading to work

For an initial connection to work, “Account data” and “Metadata” are both required.

To access the user’s history, such as filled orders, both “History” and “History - Orders” need to be selected. If these permissions are not granted, the SnapTrade /orders endpoint will return a 403.

To access the user’s pending orders, the “Orders - Read” permission needs to be granted. If it is not, the SnapTrade /orders endpoint will return a 403.

To access the user’s positions, the “Portfolio” permission needs to be granted. Otherwise, the SnapTrade /positions endpoint will return a 403.