Rate limits are counted per API key, across all endpoints together rather than per endpoint.
Going over returns 429 Too Many Requests.
Limits
GET /account is exempt from these limits, so you can check
your balance without spending your budget on it.Handling 429
The response is a plain 429 with the body Retry later. Back off exponentially and retry: unlike
400 or 422, a 429 request is worth replaying as is.
A client stuck in a retry loop that keeps firing at full speed can get the account blocked, not
just throttled. Always put a real backoff between retries, and cap the number of attempts.
Staying under the limit
- Enrich in batches.
POST /async takes up to 100 leads in a single call, which is one request
instead of a hundred.
- Use a webhook instead of polling. Polling a large batch every second is
the most common way to hit the limit for nothing.
- When you do poll, wait a few seconds between attempts. See the recipe in
Request statuses.
