Appearance
Rate limits
General limit
60 requests per minute per user. All tokens of a user share this limit; before a request is authenticated, the limit applies per IP address.
Every response carries the current state:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | requests allowed per minute |
X-RateLimit-Remaining | requests left in the current minute |
Retry-After | on a 429: seconds to wait before the next request |
http
HTTP/1.1 429 Too Many Requests
Retry-After: 23
Content-Type: application/json
{"message": "Too Many Attempts."}Orders
On top of the general limit, both order APIs allow 10 orders per minute and team:
A further order answers 429 with error: rate_limited and Retry-After. Replays of an idempotent request do not count.
Good practice
- Respect
Retry-Afterinstead of retrying right away. - Poll background operations and orders at a moderate pace (every few seconds), or use webhooks if you are an app.
- A server's
statusis read from its host at most every 15 seconds - polling it faster gives you no newer data.