Interactive Brokers API error code
Interactive Brokers API error: 429 Too Many Requests
The error, as text you can copy
429 Too Many Requests- Kind
- API error code
- HTTP status
- 429
What does 429 Too Many Requests mean on the Interactive Brokers API?
On the Client Portal Web API, Interactive Brokers says that where a pacing limit is exceeded, the API returns a "429 Too Many Requests" exception (the vendor's wording). The page states a limit of 10 requests per second, with lower limits on some endpoints. The IP address of the violator is put in a penalty box, and the vendor says repeat violators can be permanently blocked until the issue is resolved. The vendor's own pages disagree on the length of the penalty: this page and the current Web API pacing page say 10 minutes, and the Web API v1.0 pacing page says 15 minutes. All three were read on 12 October 2026.
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.
How do I fix 429 Too Many Requests?
Slow down and keep within the general limit and the limit of each endpoint. The vendor's pages say the IP address leaves the penalty box after the stated period, until another request exceeds a limit.
Interactive Brokers limits behind this error
This is a rate or allowance error, so these are the limits recorded for Interactive Brokers, each with its scope and source. Pace your requests against them.
| Limit | Value | Scope | Source |
|---|---|---|---|
| Global requests a second (Web API) | 10 | Per authenticated username, that is per Web API session | ibkrcampus.comchecked corroborated by interactivebrokers.com/docs/web-api/trading/usage-and-availability/pacing-limitations |
| Historical market data requests | Either 10 req/s or 50 req/minute, as the page words it | GET /iserver/marketdata/history only | interactivebrokers.comchecked corroborated by ibkrcampus.com/campus/ibkr-api-page/webapi-doc/ |
| Market data snapshot requests a second | 10 | GET /iserver/marketdata/snapshot only | interactivebrokers.comchecked corroborated by ibkrcampus.com/campus/ibkr-api-page/webapi-doc/ |
| Order and trade list requests | 1 req/5 s | GET /iserver/orders and GET /iserver/trades, each counted on its own | interactivebrokers.comchecked corroborated by ibkrcampus.com/campus/ibkr-api-page/webapi-doc/ |
| Session validation requests a minute | 1 | GET /sso/validate only | interactivebrokers.comchecked corroborated by ibkrcampus.com/campus/ibkr-api-page/webapi-doc/ |
| Session keep alive requests a second | 1 | GET /tickle only | interactivebrokers.comchecked corroborated by ibkrcampus.com/campus/ibkr-api-page/webapi-doc/ |