Rate Limits & Quotas¶
The SDK reference includes 8 rate limit and quota errors. These cover trading operation caps, historical data request limits, WebSocket subscription weight, and heavy polling patterns.
8 documented errors
Rate Limit Error Lookup
Search trading OPS, historical data usage, WebSocket weight, and quota errors.
Limits To Watch¶
| Area | Failure pattern | What to do |
|---|---|---|
| Trading APIs | Too many order operations per second | Queue requests and respect OPS limits. |
| Historical data | Too many requests per minute | Batch work and back off before retrying. |
| WebSocket subscriptions | Weight exceeded | Unsubscribe or reduce stream weight. |
| Option chain streams | Heavy subscription weight | Subscribe only to required instruments. |
| Aggressive polling | Repeated REST calls for live-like data | Use WebSocket where possible. |
Handling Flow¶
Rate limit or quota error
|
v
Stop immediate retry loop
|
v
Back off according to limit window
|
v
Reduce request volume or subscription weight
|
v
Retry with bounded policy
User Message¶
Use a calm user-facing message:
Too many requests were sent in a short time. Please wait while the system slows down and retries.
Developer Notes¶
- Rate limits are one of the few categories where retry can be safe after waiting.
- Do not use retries to hide inefficient polling.
- Track retry exhaustion and rate-limit frequency in monitoring.
