Rate limits

REST has two independent controls: a per-key burst limit and a per-user monthly quota (monthlyRequests). Exceeding either returns 429 with rate_limited or quota_exceeded, plus a Retry-After header. Wait that long, then retry. WebSocket traffic is not counted against the monthly REST quota.

HTTP/1.1 429 Too Many Requests
Retry-After: 2
Content-Type: application/json

{ "error": { "code": "rate_limited", "message": "…" } }

Stream event delivery is not counted against REST rate limits. Your plan limits how many concurrent streams you can run — each WebSocket connection is one stream, subscribed to a single channel. See Connection limits for details.

Subscribe and unsubscribe messages are rate-limited to 10 per second per connection. Exceeding this returns a stream error frame with code rate_limited.