# Trading 212 API rate limits Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade. This is the markdown version of https://openbrokerapi.com/brokers/trading-212/rate-limits, written from the same records as that page. Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders. What is recorded about how fast you may call the Trading 212 API: 1 limit record, the wording from the record and 1 related error code. - Newest check: 2026-10-12 ## Recorded limits One record per limit. The scope is part of the limit: a figure is only useful once you know whether it applies to a key, an account, a session or an address. - Headline limit: 1 req/5s, account summary (example) - Scope: account - Status: verified. Source: [docs.trading212.com](https://docs.trading212.com/api/section/rate-limiting), checked 2026-10-12. - Note: Limits are set per endpoint and applied per account; this is the account summary example from the docs, not a single global figure. A different endpoint on the same docs page carries a much higher limit, order placement (POST market order) at 50 requests a minute, about one call every 1.2 seconds, shown elsewhere on this site's re-verified note dated 23 Sep 2026. The two figures are not a contradiction: they are two different endpoints on one rate-limiting page, read account summary 22 Sep 2026 and order placement 23 Sep 2026. Build a rate limiter against the endpoint you actually call, not against either figure alone. ## Rate limits, as the record words them - Rate limits, as worded: Per endpoint, applied per account whatever the API key or IP: for example account summary at 1 request every 5 seconds, with the reset time in an x-ratelimit-reset header. - Status: verified. Source: [Trading 212 API docs: rate limiting](https://docs.trading212.com/api/section/rate-limiting), checked 2026-10-12. - Status: verified. Source: [Trading 212 API docs: accounts](https://docs.trading212.com/api/accounts), checked 2026-10-12. ## Error codes that concern limits These are the decoded Trading 212 errors whose record concerns a rate limit, an allowance or throttling. Each links to the full meaning and the fix. - [HTTP 429](https://openbrokerapi.com/errors/trading-212/429-rate-limit) (HTTP status 429): Too many requests for this endpoint in the current period. - Status: verified. Source: [docs.trading212.com](https://docs.trading212.com/api/section/rate-limiting), checked 2026-09-21. ## Pacing and backoff, in general This part is general advice and says nothing about Trading 212 in particular. The figures that apply are the recorded ones above, and the provider's own documentation is the authority. Pace before you are refused. Work out the gap between requests that keeps you under the limit, then leave a margin, because a limit counted by a provider's clock will not line up exactly with yours. Spread calls evenly: a burst at the start of each window is the usual way to hit a limit while staying under it on average. The rate limit calculator at https://openbrokerapi.com/tools/rate-limit-calculator checks a polling plan against a limit and gives the shortest interval that fits. When a request is refused for rate, stop sending and wait. Double the wait after each refusal in a row, add a small random amount so that several programs do not retry together, and cap the number of attempts. If the reply names how long to wait, use that figure in place of your own. Take extra care with dealing requests. A refused or unanswered order may or may not have gone through, so check the state of the order before you send it again. Cache what does not change, such as instrument details and history you have already downloaded, and prefer a stream to polling where one is offered. ## Where to go next - [The full Trading 212 record](https://openbrokerapi.com/brokers/trading-212) - [All Trading 212 error codes](https://openbrokerapi.com/errors/trading-212) - [Rate limits for every broker and platform](https://openbrokerapi.com/rate-limits) - [The fact register](https://openbrokerapi.com/facts) ## Licence and how to cite The limit records on this page come from the limits register, which is CC BY 4.0 (https://openbrokerapi.com/data/limits.json). Everything else on it comes from records that are all rights reserved. This file is the page itself, at its own address, in another format, and it is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Cite as: Trading 212 API rate limits. Broker API Hub, https://openbrokerapi.com/brokers/trading-212/rate-limits, newest check 2026-10-12. Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.