Rate limits
Limits depend on your plan. REST and streams are metered separately.
REST
REST rate limits depend on your plan (5–100 req/s). When you exceed the limit you'll get a 429 with a Retry-After header (in seconds). Wait that long, then retry.
HTTP/1.1 429 Too Many Requests
Retry-After: 2
Content-Type: application/json
{ "error": { "code": "rate_limited", "status": 429 } }Streams
Stream event delivery is not counted against REST rate limits. Your plan limits how many WebSocket connections you can have open at once — not how many channels you subscribe to on each connection. 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.