What are the default rate limits?
Every POST endpoint allows 20 requests per second per API key, averaged over 10-second windows. The limit is identical across all endpoints and all plans:
The limit is counted over fixed 10-second windows. Each endpoint accepts up to 200 requests per window, and at most 40 requests in any single second. You can therefore send short bursts above 20 req/s, as long as the total of the window stays within 200.
GET endpoints are not rate limited, so retrieving results — for example the single email result or bulk results — does not count against your quota.
Rate limits are per API key and measured in requests per second (RPS). Each API key has its own independent quota.
What happens when I exceed the rate limit?
When you exceed the rate limit, the API returns a429 Too Many Requests response with a Retry-After header:
Retry-After header gives the number of seconds to wait before sending again: 1 after a burst (more than 40 requests in one second), and up to 10 when the 200 requests of the current window are used up. A refused request does not count against your quota.
The recommended way to handle a 429 is to wait for the delay given by Retry-After before retrying, and to fall back to exponential backoff when the header is missing:
How can I avoid hitting the rate limit?
The most effective way to stay within quota is to send fewer, larger requests and to receive results through webhooks instead of polling.Use bulk endpoints
Use bulk endpoints
Instead of making 100 single requests, make 1 bulk request (up to 5,000 items for email, 3,000 for phone). A single bulk POST counts as 1 request against your rate limit.See Find Bulk Emails and Verify Bulk Emails to get started.
Use webhooks instead of polling
Use webhooks instead of polling
Polling the GET endpoint wastes your rate limit quota. Use webhooks to receive results automatically as soon as a search or verification completes.
Cache results
Cache results
Store results to avoid redundant API calls for the same contact, which also saves credits.
Can I get higher rate limits?
Yes. Enrow can increase your RPS on a case-by-case basis. Contact us at api@enrow.io with your use case and expected volume.FAQ
Do GET requests count against the rate limit?
Do GET requests count against the rate limit?
No. GET endpoints are not rate limited, so polling for results does not consume your RPS quota. That said, webhooks are still preferable to frequent polling.
Does a bulk request count as one request?
Does a bulk request count as one request?
Yes. A single bulk POST counts as 1 request against your rate limit, even though it can contain up to 5,000 items for email or 3,000 for phone.
What status code signals a rate limit error?
What status code signals a rate limit error?
A
429 Too Many Requests response with the body { "message": "Too Many Requests" } and a Retry-After header. Wait for that delay before retrying. See Error handling for details.Next steps
Find emails in bulk
Run up to 5,000 email searches in a single request to save rate limit quota.
Webhooks
Receive results automatically instead of polling the GET endpoints.
Error handling
Handle 429 and other responses gracefully in your integration.
Credits & billing
See how credits are consumed for each endpoint.

