| Requests | Limit |
|---|---|
Reads (GET, HEAD, OPTIONS) — authenticated | 1,800 per minute |
Writes (POST, PUT, PATCH, DELETE) — authenticated | 600 per minute |
| Reads — unauthenticated (public endpoints) | 1,800 per minute per IP |
| Writes — unauthenticated | 60 per minute per IP |
Handling 429 Too Many Requests
When you exceed a limit the API returns HTTP 429, and the response includes a Retry-After header with the number of seconds to wait:
Retry-After, and add jittered exponential backoff around bursts. A few practical tips:
- Poll gently. Ticker prices don’t change faster than a few times per second — polling
GET /api/public/broker/ticker/more than once a second gains you nothing. - Batch reads. The ticker and balances endpoints return all assets in one call; don’t fetch per-asset in a loop.
- After creating a swap, poll its status about once per second for up to ~10 seconds — that is well inside the limits.