Rate limits
How many requests you can make and how to tell when you are close to the limit.
The API allows 300 requests per minute per client IP address, counted across all endpoints in fixed one-minute windows. The limit is per IP, not per API key, so services that share an outbound IP share the budget.
Rate limit headers
Every response tells you where you stand:
| Header | Description |
|---|---|
RateLimit-Limit | Requests allowed in the window (300). |
RateLimit-Remaining | Requests left in the current window. |
RateLimit-Reset | Seconds until the window resets. |
RateLimit-Policy | The policy in effect, for example 300;w=60. |
Retry-After | Only on 429 responses: seconds to wait before trying again. |
HTTP/1.1 200 OK
RateLimit-Policy: 300;w=60
RateLimit-Limit: 300
RateLimit-Remaining: 287
RateLimit-Reset: 41When you hit the limit
Requests over the limit get 429 Too Many Requests with a Retry-After header and the usual JSON envelope:
{
"status": "error",
"message": "RATE_LIMITED",
"data": { "message": "Too many requests. Slow down and retry after the time in the RateLimit-Reset header." }
}Staying under the limit
- Wait for
Retry-Afterseconds before retrying a 429, then back off exponentially if it repeats. - Watch
RateLimit-Remainingand slow down before it reaches zero. - Use webhooks instead of polling for payout and collection status.
- Cache data that rarely changes, such as bank lists and payout requirements.