Trading 212 API

Note: The Trading 212 API is currently in beta and under active development. Some endpoints or behaviors may change.

Quick Reference

Environments

Environment	Base URL	Purpose
Demo	INLINECODE0	Paper trading - test without real funds
Live

https://live.trading212.com/api/v0 | Real money trading |

Order Quantity Convention

• - Positive quantity = BUY (e.g., 10 buys 10 shares)
• Negative quantity = SELL (e.g., -10 sells 10 shares)

Account Types

Only Invest and Stocks ISA accounts are supported.

Instrument Identifiers

Trading 212 uses custom tickers as unique identifiers for instruments.
Always search for the Trading 212 ticker before making instrument requests.

---

Authentication

HTTP Basic Auth with API Key (username) and API Secret (password).

Check Existing Setup First

Before guiding the user through authentication setup, check if credentials are already configured:

Semantic rule: Credentials are configured when at least one complete set is present: a complete set is key + secret for the same account (e.g. T212_API_KEY + T212_API_SECRET, or T212_API_KEY_INVEST + T212_API_SECRET_INVEST, or T212_API_KEY_STOCKS_ISA + T212_API_SECRET_STOCKS_ISA). You do not need all four account-specific vars; having only the Invest pair or only the Stocks ISA pair is enough. Check for any combination that gives at least one usable key+secret pair.

CODEBLOCK0

If any complete set is present, skip the full setup and proceed with API calls; when making requests, use the resolution order in "Making Requests" below (pick the pair that matches the user's account context when multiple sets exist). Do not ask the user to run derivation one-liners or merge keys into a header. Only guide users through the full setup process below when no complete credential set exists.

Important: Before making any API calls, always ask the user which environment they want to use: LIVE (real money) or DEMO (paper trading). Do not assume the environment.

API Keys Are Environment-Specific

API keys are tied to a specific environment and cannot be used across environments.

API Key Created In	Works With	Does NOT Work With
LIVE account	INLINECODE10	INLINECODE11
DEMO account

demo.trading212.com | live.trading212.com |

If you get a 401 error, verify that:

1. 1. You're using the correct API key for the target environment
2. The API key was generated in the same environment (LIVE or DEMO) you're trying to access

Get Credentials

1. 1. Decide which environment to use - LIVE (real money) or DEMO (paper trading)
2. Open Trading 212 app (mobile or web)
3. Switch to the correct account - Make sure you're in LIVE or DEMO mode matching your target environment
4. Navigate to Settings > API
5. Generate a new API key pair - you'll receive:

- API Key (ID) (e.g., 35839398ZFVKUxpHzPiVsxKdOtZdaDJSrvyPF) - API Secret (e.g., 7MOzYJlVJgxoPjdZJCEH3fO9ee7A0NzLylFFD4-3tlo)

1. 6. Store the credentials separately for each environment if you use both

Building the Auth Header

Combine your API Key (ID) and Secret with a colon, base64 encode, and prefix with Basic for the Authorization header.

Optional: To precompute the header from key/secret, you can set:

CODEBLOCK1

Otherwise, the agent builds the header from T212_API_KEY and T212_API_SECRET when making requests.

Manual (placeholders):

CODEBLOCK2

Making Requests

When making API calls, use the first option that applies (semantically: pick the credential set that matches the user's account, or the only set present):

• - If T212_AUTH_HEADER and T212_BASE_URL are set: use them in requests.
• Else if T212_API_KEY and T212_API_SECRET are set: use this pair (single account). Build header as Basic $(echo -n "$T212_API_KEY:$T212_API_SECRET" | base64) and base URL as https://${T212_ENV:-live}.trading212.com. Do not guide the user to derive or merge; you do it.
• Else if both account-specific pairs are set (T212_API_KEY_INVEST/T212_API_SECRET_INVEST and T212_API_KEY_STOCKS_ISA/T212_API_SECRET_STOCKS_ISA): the user must clearly specify which account to target (Invest or Stocks ISA), unless they ask for information for all accounts. Use the Invest pair when the user refers to Invest, and the Stocks ISA pair when the user refers to ISA/Stocks ISA. If the user wants information for all accounts, make multiple API calls—one per account (Invest and Stocks ISA)—and present or aggregate the results for both. If it is not clear from context which account to use (and they did not ask for all accounts), ask for confirmation before making API calls (e.g. "Which account should I use — Invest or Stocks ISA?"). Do not assume. Build the header from the chosen key/secret and base URL as https://${T212_ENV:-live}.trading212.com.
• Else if only the Invest pair is set (T212_API_KEY_INVEST and T212_API_SECRET_INVEST): use this pair for requests; if the user asks about Stocks ISA, only the Invest account is configured.
• Else if only the Stocks ISA pair is set (T212_API_KEY_STOCKS_ISA and T212_API_SECRET_STOCKS_ISA): use this pair for requests; if the user asks about Invest, only the Stocks ISA account is configured.

Use the T212_AUTH_HEADER value in the Authorization header when it is set:

CODEBLOCK3

When only primary vars are set, use the inline form in the curl:

CODEBLOCK4

Warning: T212_AUTH_HEADER must be the full header value including the Basic prefix.
CODEBLOCK5

Environment Variables

Single account vs all accounts: API keys are for a single account. One key/secret pair (T212_API_KEY + T212_API_SECRET) = one account (Invest or Stocks ISA). To use all accounts (Invest and Stocks ISA), the user must set two sets of key/secret: T212_API_KEY_INVEST / T212_API_SECRET_INVEST and T212_API_KEY_STOCKS_ISA / T212_API_SECRET_STOCKS_ISA. When both pairs are set, the user must clearly specify which account to target; if it is not clear from context, ask for confirmation (Invest or Stocks ISA) before making API calls.

Primary (single account): Set these for consistent setup with the plugin README:

CODEBLOCK6

Account-specific (Invest and/or Stocks ISA): Set only the pair(s) you use. One complete set (key + secret for the same account) is enough. For example, only Invest:

CODEBLOCK7

For both accounts, set both pairs:

CODEBLOCK8

Optional – precomputed (for scripts or if the user prefers): The user can set the auth header and base URL from the primary vars, but they do not need to; when making API calls you (the agent) must build the header and base URL from primary vars if these are not set.

CODEBLOCK9

Alternative (manual): If you prefer not to store key/secret in env, set derived vars directly. Remember: API keys only work with their matching environment.

CODEBLOCK10

Tip: If you use both environments, use separate variable names:

CODEBLOCK11

Common Auth Errors

Code	Cause	Solution
401	Invalid credentials	Check API key/secret, ensure no extra whitespace
401

Environment mismatch | LIVE API keys don't work with DEMO and vice versa - verify key matches target environment | | 403 | Missing permissions | Check API permissions in Trading 212 settings | | 408 | Request timed out | Retry the request | | 429 | Rate limit exceeded | Wait for x-ratelimit-reset timestamp |

---

Account

Get Account Summary

INLINECODE44 (1 req/5s)

CODEBLOCK12

Response Schema:

CODEBLOCK13

Account Fields

Field	Type	Description
INLINECODE45	integer	Primary trading account number
INLINECODE46

string | Primary account currency (ISO 4217) | | totalValue | number | Total account value in primary currency | | cash.availableToTrade | number | Funds available for investing | | cash.reservedForOrders | number | Cash reserved for pending orders | | cash.inPies | number | Uninvested cash inside pies | | investments.currentValue | number | Current value of all investments | | investments.totalCost | number | Cost basis of current investments | | investments.realizedProfitLoss | number | All-time realized P&L | | investments.unrealizedProfitLoss | number | Potential P&L if sold now |

---

Orders

Order Types

Type	Endpoint	Availability	Description
Market	INLINECODE55	Demo + Live	Execute immediately at best price
Limit

/api/v0/equity/orders/limit | Demo + Live | Execute at limit price or better | | Stop | /api/v0/equity/orders/stop | Demo + Live | Market order when stop price reached | | StopLimit | /api/v0/equity/orders/stop_limit | Demo + Live | Limit order when stop price reached |

Order Statuses

Status	Description
INLINECODE59	Order created locally, not yet sent
INLINECODE60

Sent to exchange, awaiting confirmation | | CONFIRMED | Confirmed by exchange | | NEW | Active and awaiting execution | | CANCELLING | Cancel request in progress | | CANCELLED | Successfully cancelled | | PARTIALLY_FILLED | Some shares executed | | FILLED | Completely executed | | REJECTED | Rejected by exchange | | REPLACING | Modification in progress | | REPLACED | Successfully modified |

Time Validity

Value	Description
INLINECODE70	Expires at midnight in exchange timezone
INLINECODE71

Active until filled or cancelled (default) |

Order Strategy

Value	Description
INLINECODE72	Order by number of shares (API supported)
INLINECODE73

Order by monetary value (not supported via API) |

Initiated From

Value	Description
INLINECODE74	Placed via this API
INLINECODE75

iOS app | | ANDROID | Android app | | WEB | Web platform | | SYSTEM | System-generated | | AUTOINVEST | Autoinvest feature |

Place Market Order

INLINECODE80 (50 req/min)

CODEBLOCK14

Request Fields:

Field	Type	Required	Description
INLINECODE81	string	Yes	Instrument ticker (e.g., AAPL_US_EQ)
INLINECODE83

number | Yes | Positive for buy, negative for sell |
| extendedHours | boolean | No | Set true to allow execution in pre-market (4:00-9:30 ET) and after-hours (16:00-20:00 ET) sessions. Default: false |

Response:

CODEBLOCK15

Place Limit Order

INLINECODE87 (1 req/2s)

CODEBLOCK16

Request Fields:

Field	Type	Required	Description
INLINECODE88	string	Yes	Instrument ticker
INLINECODE89

number | Yes | Positive for buy, negative for sell |
| limitPrice | number | Yes | Maximum price for buy, minimum for sell |
| timeValidity | string | No | DAY (default) or GOOD_TILL_CANCEL |

Place Stop Order

INLINECODE94 (1 req/2s)

CODEBLOCK17

Request Fields:

Field	Type	Required	Description
INLINECODE95	string	Yes	Instrument ticker
INLINECODE96

number | Yes | Positive for buy, negative for sell |
| stopPrice | number | Yes | Trigger price (based on Last Traded Price) |
| timeValidity | string | No | DAY (default) or GOOD_TILL_CANCEL |

Place Stop-Limit Order

INLINECODE101 (1 req/2s)

CODEBLOCK18

Request Fields:

Field	Type	Required	Description
INLINECODE102	string	Yes	Instrument ticker
INLINECODE103

number | Yes | Positive for buy, negative for sell |
| stopPrice | number | Yes | Trigger price to activate limit order |
| limitPrice | number | Yes | Limit price for the resulting order |
| timeValidity | string | No | DAY (default) or GOOD_TILL_CANCEL |

Get Pending Orders

INLINECODE109 (1 req/5s)

CODEBLOCK19

Returns array of Order objects with status NEW, PARTIALLY_FILLED, etc.

Get Order by ID

INLINECODE110 (1 req/1s)

CODEBLOCK20

Cancel Order

INLINECODE111 (50 req/min)

CODEBLOCK21

Returns 200 OK if cancellation request accepted. Order may already be filled.

Common Order Errors

Error	Cause	Solution
INLINECODE112	Not enough cash	Check INLINECODE113
INLINECODE114

Selling more than owned | Check quantityAvailableForTrading | | MarketClosed | Outside trading hours | Check exchange schedule |

---

Positions

Get All Positions

INLINECODE117 (1 req/1s)

Query Parameters:

Parameter	Type	Required	Description
INLINECODE118	string	No	Filter by specific ticker (e.g., AAPL_US_EQ)

CODEBLOCK22

Response Schema:

CODEBLOCK23

Position Fields

Field	Type	Description
INLINECODE120	number	Total shares owned
INLINECODE121

number | Shares available to sell | | quantityInPies | number | Shares allocated to pies | | currentPrice | number | Current price (instrument currency) | | averagePricePaid | number | Average cost per share | | createdAt | datetime | Position open date | | walletImpact.currency | string | Account currency | | walletImpact.totalCost | number | Total cost in account currency | | walletImpact.currentValue | number | Current value in account currency | | walletImpact.unrealizedProfitLoss | number | P&L in account currency | | walletImpact.fxImpact | number | Currency rate impact on value |

Position Quantity Scenarios

Scenario	quantity	quantityAvailableForTrading	quantityInPies
All direct holdings	10	10	0
Some in pie

10 | 7 | 3 | | All in pie | 10 | 0 | 10 |

Important: Always check quantityAvailableForTrading before placing sell orders.

---

Instruments

Ticker Lookup Workflow

When users reference instruments by common names (e.g., "SAP", "Apple", "AAPL"), you must look up the exact Trading 212 ticker before making any order, position, or historical data queries. Never construct ticker formats manually.

CACHE FIRST: Always check /tmp/t212_instruments.json before calling the API. The instruments endpoint has a 50-second rate limit and returns ~5MB. Only call the API if cache is missing or older than 1 hour.

Generic search: Match the user's search term in the three meaningful fields: ticker, name, or shortName. Use one variable (e.g. SEARCH_TERM) with test($q; "i") on each field so "TSLA", "Tesla", "TL0", etc. match efficiently. For regional filtering (e.g. "US stocks", "European SAP"), use the ISIN prefix (first 2 characters) for country code or currencyCode after the grep.

IMPORTANT: Never auto-select instruments. If multiple options exist, you are required to ask the user for their preference.

CODEBLOCK24

Get All Instruments

INLINECODE136 (1 req/50s)

CODEBLOCK25

Response Schema:

CODEBLOCK26

Instrument Fields

Field	Type	Description
INLINECODE137	string	Unique instrument identifier
INLINECODE138

string | Full instrument name | | shortName | string | Short symbol (e.g., AAPL) | | isin | string | International Securities ID | | currencyCode | string | Trading currency (ISO 4217) | | type | string | Instrument type (see below) | | maxOpenQuantity | number | Maximum position size allowed | | extendedHours | boolean | Whether extended hours trading is available | | workingScheduleId | integer | Reference to exchange schedule | | addedOn | datetime | When added to platform |

Instrument Types

Type	Description
INLINECODE147	Common stock
INLINECODE148

Exchange-traded fund | | CRYPTOCURRENCY | Cryptocurrency | | CRYPTO | Crypto asset | | FOREX | Foreign exchange | | FUTURES | Futures contract | | INDEX | Index | | WARRANT | Warrant | | CVR | Contingent value right | | CORPACT | Corporate action |

Ticker Format

INLINECODE157 - Examples:

• - AAPL_US_EQ - Apple on US exchange
• INLINECODE159 - Vanguard S&P 500 on London
• INLINECODE160 - Bitcoin

Get Exchange Metadata

INLINECODE161 (1 req/30s)

CODEBLOCK27

Response Schema:

CODEBLOCK28

Time Event Types

Type	Description
INLINECODE162	Pre-market session starts
INLINECODE163

Regular trading starts | | BREAK_START | Trading break begins | | BREAK_END | Trading break ends | | CLOSE | Regular trading ends | | AFTER_HOURS_OPEN | After-hours session starts | | AFTER_HOURS_CLOSE | After-hours session ends | | OVERNIGHT_OPEN | Overnight session starts |

---

Historical Data

All historical endpoints use cursor-based pagination with nextPagePath.

Pagination Parameters

Parameter	Type	Default	Max	Description
INLINECODE171	integer	20	50	Items per page
INLINECODE172

string/number | - | - | Pagination cursor (used in nextPagePath) | | ticker | string | - | - | Filter by ticker (orders, dividends) | | time | datetime | - | - | Pagination time (used in nextPagePath for transactions) |

Pagination Example

CODEBLOCK29

Historical Orders

INLINECODE177 (50 req/min)

CODEBLOCK30

Response Schema:

CODEBLOCK31

Fill Types

Type	Description
INLINECODE178	Regular trade execution
INLINECODE179

Stock split adjustment | | STOCK_DISTRIBUTION | Stock distribution | | FOP | Free of payment transfer | | FOP_CORRECTION | FOP correction | | CUSTOM_STOCK_DISTRIBUTION | Custom stock distribution | | EQUITY_RIGHTS | Equity rights issue |

Trading Methods

Method	Description
INLINECODE185	Traded on trading venue
INLINECODE186

Over-the-counter |

Tax Types (walletImpact.taxes)

Type	Description
INLINECODE187	Commission on turnover
INLINECODE188

FX conversion fee | | FINRA_FEE | FINRA trading activity fee | | FRENCH_TRANSACTION_TAX | French FTT | | PTM_LEVY | Panel on Takeovers levy | | STAMP_DUTY | UK stamp duty | | STAMP_DUTY_RESERVE_TAX | UK SDRT | | TRANSACTION_FEE | General transaction fee |

Historical Dividends

INLINECODE195 (50 req/min)

CODEBLOCK32

Response Schema:

CODEBLOCK33

Dividend Types (Common)

Type	Description
INLINECODE196	Regular dividend
INLINECODE197

Bonus dividend | | INTEREST | Interest payment | | DIVIDEND | Generic dividend | | CAPITAL_GAINS | Capital gains distribution | | RETURN_OF_CAPITAL | Return of capital | | PROPERTY_INCOME | Property income (REITs) | | DEMERGER | Demerger distribution | | QUALIFIED_INVESTMENT_ENTITY | QIE distribution | | TRUST_DISTRIBUTION | Trust distribution |

Note: Many additional US tax-specific types exist for 1042-S reporting.

Account Transactions

INLINECODE206 (50 req/min)

Pagination:

• - First request: Must use only the limit parameter (no cursor, no timestamp)
• Subsequent requests: Use the nextPagePath from the previous response, which includes cursor and timestamp automatically
• Time filtering: Transactions cannot be filtered by time - pagination is the only way to navigate through historical data

CODEBLOCK34

Response Schema:

CODEBLOCK35

Transaction Types

Type	Description
INLINECODE209	Funds deposited to account
INLINECODE210

Funds withdrawn from account | | FEE | Fee charged | | TRANSFER | Internal transfer |

CSV Reports

Request report: POST /api/v0/equity/history/exports (1 req/30s)

CODEBLOCK36

Response:

CODEBLOCK37

Poll for completion: GET /api/v0/equity/history/exports (1 req/min)

CODEBLOCK38

Response:

CODEBLOCK39

Download the report:

CODEBLOCK40

Report Status Values

Status	Description
INLINECODE215	Report request received
INLINECODE216

Report generation started | | Running | Report actively generating | | Finished | Complete - downloadLink available | | Canceled | Report cancelled | | Failed | Generation failed |

---

Pre-Order Validation

Before BUY - Check Available Funds

CODEBLOCK41

Before SELL - Check Available Shares

CODEBLOCK42

---

Rate Limit Handling

Understanding Rate Limits

Rate limits are per-account, not per API key or IP address. If you have multiple applications using the same Trading 212 account, they share the same rate limit pool.

Response Headers

Every API response includes rate limit headers:

Header	Description
INLINECODE221	Total requests allowed in period
INLINECODE222

Time period in seconds |
| x-ratelimit-remaining | Requests remaining |
| x-ratelimit-reset | Unix timestamp when limit resets |
| x-ratelimit-used | Requests already made |

Avoid Burst Requests to avoid Rate Limiting

Do not send requests in bursts. Even if an endpoint allows 50 requests per minute, sending them all at once can trigger rate limiting and degrade performance.
Pace your requests evenly, for example, by making one call every 1.2 seconds, ensuring you always stay within the limit.

Bad approach (bursting):

CODEBLOCK43

Good approach (paced):

CODEBLOCK44

Caching Strategy

For data that doesn't change frequently, cache locally to reduce API calls:

CODEBLOCK45

---

Safety Guidelines

1. 1. Test in demo first - Always validate workflows before live trading
2. Validate before ordering - Check funds (cash.availableToTrade) before buy, positions (quantityAvailableForTrading) before sell
3. Confirm destructive actions - Order placement and cancellation are irreversible
4. API is not idempotent - Duplicate requests may create duplicate orders
5. Never log credentials - Use environment variables
6. Respect rate limits - Space requests evenly, never burst
7. Max 50 pending orders - Per ticker, per account
8. Cache metadata - Instruments and exchanges change rarely