Skip to main content
Encrata caps how many requests your account can make in a short window to keep the API fast and fair for everyone. This page explains the limit, the headers on lookup responses, what a rejection looks like, and how to handle it.

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 with 429 Too Many Requests and this body:
Inspect the headers on any response with curl -i:
A successful response reports the current limit state:
Once the budget is spent, the same request returns a 429. Use X-Ratelimit-Reset to time your retry:

Retry safely

When you get a 429, 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.