Rate limits

Requests are rate limited per key. The default is 60 requests per minute; a custom limit can be set on a key. Every response carries the current limit state.

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 58
X-RateLimit-Reset: 1717619400

Limits are applied per API key (dashboard and session calls are limited per user) over a sliding 60-second window. The default is 60 requests per minute; a custom limit can be set on individual keys, and higher limits are available on request via support.

When you exceed the limit you get 429 Too Many Requests. The wait time comes from the Retry-After header (seconds), and the body is the standard v1 error envelope:

HTTP/1.1 429 Too Many Requests
Retry-After: 12

{
  "ok": false,
  "request_id": "req_8f2c1a90b3d44e01",
  "error": { "code": "rate_limited", "message": "Too many requests. Slow down and retry." }
}

A 429 never consumes credits.

One nuance: a 429 can also come from the upstream platform blocking the fetch rather than from your key's limit. Those carry the block reason (for example bot_gate or ip_blocked) as error.code instead of rate_limited, and are retryable the same way.