Rate Limits
To ensure fair usage and prevent abuse, we enforce rate limits on our API endpoints. Different endpoints have different rate limits based on their computational cost and impact on our systems.
General Rate Limiting
If the request rate exceeds the limit in any endpoints, the request will be blocked for 30 seconds. When blocked, HTTP response is 429 Too Many Requests. The limits apply to individual user accessing the API. The rate limit is applied to each endpoint regardless the API version.
Endpoint Rate Limits
Loading rate limits...
Best Practices
Implement Exponential Backoff
When you receive a 429 response, wait before retrying. Start with 1 second and double the wait time for each subsequent retry.
Cache Public Data
Cache responses from public endpoints like symbols, server time, and status to reduce unnecessary API calls.
Use WebSocket for Real-time Data
For real-time market data, use WebSocket connections instead of polling REST endpoints repeatedly.
Monitor Your Usage
Keep track of your API usage and implement client-side rate limiting to stay within bounds.
Batch Operations
When possible, batch multiple operations together instead of making individual API calls.