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.

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.

Similarly, depending on the permissions granted, the /holdings endpoint may return incomplete data. Without the Orders-related permissions granted, this endpoint will return an empty list for orders. Without the Portfolio permission, this endpoint will return an empty list for positions.

trading212-api-key-permissions.png