Rate Limits

StandX API enforces rate limits to ensure platform stability and fair resource allocation across all users. Rate limits are applied using a credit-based token bucket system.

Account Level Credit Budget

Each user address maintains a credit bucket that replenishes at a constant rate. Every API request consumes a fixed number of credits from the bucket. Once the bucket is depleted, subsequent requests will be rejected until enough credits have been replenished.

Requests that exceed the available credit balance will receive an HTTP 429 Too Many Requests response.

IP Level Credit Budget

Requests from a single IP address are limited to 50 requests per second. Exceeding this threshold will result in an HTTP 429 Too Many Requests response. This limit is subject to adjustment based on current market and system conditions.

WebSocket Connections

Best Practices

• Use WebSocket subscriptions for real-time data instead of polling REST endpoints.
• Batch requests where possible to reduce the total number of calls.
• Implement backoff logic to handle 429 responses gracefully — avoid retrying immediately.
• Monitor usage and distribute requests evenly across the budget window to prevent bursts.

Note

StandX reserves the right to adjust rate limit parameters at any time based on system load and operational requirements. Abuse or excessive usage patterns may result in temporary or permanent restrictions.