Rate Limits
Authenticated API requests are limited per API key and per account plan. Responses include rate-limit headers so clients can back off before they hit a hard limit.
How it works today
Each authenticated request consumes both an API-key bucket and an account bucket. The stricter bucket determines the response headers. If either bucket is exhausted, the API returns 429 Too Many Requests with a Retry-After header. A shared platform throttle still protects overall service stability.
Plan Limits
| Plan | Requests/minute |
|---|---|
| Free | 10 |
| Starter | 60 |
| Professional | 300 |
| Business | 1,000 |
| Enterprise | 5,000 |
Response Headers
X-RateLimit-Limit: requests allowed in the current window.X-RateLimit-Remaining: requests remaining in the current window.X-RateLimit-Reset: Unix timestamp when the current window resets.X-RateLimit-Window: window length in seconds.Retry-After: seconds to wait after a 429 response.
If you receive a 429
A 429 indicates the current key or account window is exhausted. Wait for theRetry-After value, then retry with jittered backoff if needed.
Best Practices
Use Batch Endpoints
For verifying multiple emails, use /v1/verify/batch instead of making many individual requests.
Cache Results
Verification results are cached for 24 hours. Take advantage of this to reduce API calls.
Back Off on 429
Retry with increasing, jittered delays rather than tight loops, so the platform can recover.
High-volume needs
Planning a high-volume integration? Talk to us so we can make sure you have the capacity and the right plan for your workload.
Contact Sales