Rate Limits
The IB Partner API applies rate limiting to protect service availability and prevent abuse.
Limits
| Limit type | Details |
|---|---|
| Request rate | 100 requests per minute per API key |
| Failed lookups | Repeated failed lookups within a short window trigger a temporary 429 response |
Handling 429 responses
When you receive a 429 Too Many Requests, your integration should:
- Stop retrying immediately — sending more requests extends the lock-out window.
- Wait — pause for at least 60 seconds before trying again.
- Implement exponential back-off — on subsequent retries, double the wait time (60 s → 120 s → 240 s…).
- Check your logic — repeated 400 errors from invalid
user_idvalues also count toward the failed-lookup limit.
Best practices
- Validate
user_idclient-side before calling the API. Only send UUIDs that you have reasonable confidence exist. - Cache successful results where your use-case allows —
is_under_ibanddate_joinedrarely change in short windows. - Do not poll aggressively — this API is designed for on-demand checks, not continuous monitoring.