# Trading 212 API error: HTTP 429

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/errors/trading-212/429-rate-limit, 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.

The error, as text you can copy:

```
HTTP 429
```

- Kind: API error code
- HTTP status: 429
- API: [Trading 212](https://openbrokerapi.com/brokers/trading-212)
- Status: verified. Source: [docs.trading212.com](https://docs.trading212.com/api/section/rate-limiting), checked 2026-09-21.

## What does HTTP 429 mean on the Trading 212 API?

Too many requests for this endpoint in the current period. The endpoint reference lists 429 as a response and sets a limit per endpoint, for example 1 request every 5 seconds for the account summary, and the limits apply per account, whichever key or IP address sends the request.

## How do I fix HTTP 429?

Pace each endpoint to the limit on its reference page, read x-ratelimit-remaining before each call, and when it reaches zero wait until the Unix time in x-ratelimit-reset.

## Trading 212 limits behind this error

This is a rate or allowance error, so these are the limits recorded for Trading 212, each with its scope and source. Pace your requests against them.

- 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.

## More on the Trading 212 API

- [All Trading 212 API error codes](https://openbrokerapi.com/errors/trading-212)
- [Trading 212 API quickstart](https://openbrokerapi.com/brokers/trading-212/quickstart): From credentials to a first call on a demo account, step by step.
- [Trading 212 API error codes](https://openbrokerapi.com/errors/trading-212): 8 decoded, each with what it means, and the fix where the source gives one.
- [Trading 212 API endpoints](https://openbrokerapi.com/brokers/trading-212/endpoints): 16 documented, each with its method, path, parameters and source.
- [Trading 212 API page](https://openbrokerapi.com/brokers/trading-212): The full record: access, authentication, limits and the source for each.
- [Export Trading 212 trade history to Excel or a spreadsheet](https://openbrokerapi.com/guides/trading-212-trade-history): Guide

## Licence and how to cite

The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page.

Cite as: Trading 212 API error: HTTP 429. Broker API Hub, https://openbrokerapi.com/errors/trading-212/429-rate-limit, newest check 2026-09-21.

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.