How the limit works
Each account is limited to 200 requests per minute by default, on a rolling 1-minute window. The limit is enforced per account, not per API key. All of an account’s keys draw from the same budget, so creating extra keys does not raise your ceiling. It only helps you organize and revoke access.Higher limits are available on some plans and on request. Contact support to
raise your account’s limit.
Response headers
Lookup responses carry the current state of your limit, so you can pace requests without guessing./api/account/* and /api/health responses do not carry
rate-limit headers. 429 responses don’t include Retry-After.
When you exceed the limit
Over the limit, the API responds with429 Too Many Requests and this body:
curl -i:
429. Use X-Ratelimit-Reset to time your retry:
Retry safely
When you get a429, wait X-Ratelimit-Reset seconds, then retry. If the header
is missing, fall back to exponential backoff. Cap the number of attempts so a
client never loops forever:
Best practices
Honor X-Ratelimit-Reset
Wait the
X-Ratelimit-Reset seconds before retrying, instead of a fixed delay.Spread requests
Distribute calls evenly across the window rather than bursting.
Use bulk endpoints
For high-volume lookups, batch with bulk endpoints instead of single calls.
Watch remaining
Slow down when
X-Ratelimit-Remaining gets low, before you hit 429.Next steps
- Errors: Every status code and how to recover from it.
- Bulk operations: Process large volumes without hitting per-request limits.