Help centerAccount and support
Limits and common errors
Plain-language answers to common Email Finder Verifier API errors: 401, 402, 429, timeouts and what to do about each.
When something goes wrong, our service sends back an error code. It's a short number that tells you what happened.
Two ideas first.
- Rate limit: how fast you may send requests. A request is one question you send to our service. New accounts can send 1 request per second.
- Concurrent requests: requests running at the same moment. New accounts can have 5 at once.
| You see | Why | What to do |
|---|---|---|
401 INVALID_API_KEY |
The key is missing, wrong or deleted. | Check the key you pasted. Make sure it's in the X-API-Key header (an extra line of information sent along with a request). Check it still exists under API keys in the dashboard. |
402 OUT_OF_CREDITS |
Your free allowance is used up. | Ask us on Slack to extend it. |
429 RATE_LIMIT_EXCEEDED |
You sent requests too fast. | Slow down to 1 request per second. Wait a moment and try again. |
429 CONCURRENT_LIMIT_EXCEEDED |
More than 5 requests were running at once. | Run fewer at the same time. |
| A request takes a while | Some checks take several seconds. | Set a timeout of at least 60 seconds. A timeout is how long your tool waits before it gives up. |
OUT_OF_CREDITS and credits_left are only code names. There are no credits. A 402 means you have used your free allowance.
Full details: Limits and Errors.
Still stuck?
Ask us on Slack. Tell us the error code you saw.
Still stuck? Ask us on Slack. Real people answer.
Get supportLast updated 16.11.2026