Skip to main content

​
REST

When limits exist, the API should return 429 Too Many Requests (or your chosen status) with enough detail to retry safely. Prefer exponential backoff and respect Retry-After when provided. Document concrete limits (per IP, per key, per route) here once product publishes them.

​
WebSockets

Prefer streams for high-frequency market and account data instead of polling REST. If the server disconnects you after idle or flood behavior, reconnect with jitter and resubscribe using the same messages described in the WebSocket reference.