Running into a problem? Here are solutions to the most common issues EmailKit users encounter.
Problem: You're trying to verify an email but getting an "Insufficient credits" error.
Solution:
Check your credit balance on the Billing page
If your balance is zero or too low, buy more credits
For bulk verification, you need enough credits for the entire list upfront
Problem: You can't log in to your EmailKit account.
Solutions:
Forgot password? Click "Forgot Password" on the sign-in page to reset it
Google Sign-In not working? Try clearing your browser cookies, or use an incognito/private window
Getting a 401 error? Your session may have expired. Try signing in again
Account locked? Contact support@emailkit.dev
Problem: Your bulk verification job seems stuck or isn't progressing.
Solutions:
Bulk jobs process emails in batches. If you have thousands of emails, it may take several minutes
Refresh the page to see updated progress
If a job has been stuck at the same percentage for more than 10 minutes, contact support
You can only run one bulk job at a time — make sure you don't have another job in progress
Problem: Your CSV file won't upload or is returning an error.
Solutions:
File too large? Maximum file size is 25 MB. Split your file into smaller chunks
Wrong format? Only CSV (.csv) and Excel (.xlsx) files are supported
Encoding issues? Save your CSV with UTF-8 encoding
Missing headers? The first row should contain column headers
No email column detected? Make sure at least one column contains email addresses. You can manually select the email column after upload
Quotes or special characters? If emails contain unusual characters, try cleaning the file first
Problem: API requests return a 401 Unauthorized error.
Solutions:
Verify you're using the correct API key (starts with ek_)
Check that you're passing it in the Authorization header as Bearer ek_your_key_here
Make sure the key hasn't been revoked — check the API Keys page
If the key has an expiration date, check if it's expired
Test keys (ek_test_...) return mock results — make sure you're using the right key type
Problem: API requests are returning 429 Too Many Requests.
Solutions:
You're exceeding 50 requests per second or 30 concurrent requests
Implement exponential backoff in your code
Check the X-RateLimit-Remaining header to throttle proactively
Consider using the batch endpoint (up to 100 emails per request) instead of individual requests
For large volumes, use the bulk endpoint instead
Problem: An email is returning an "Unknown" status instead of deliverable/undeliverable.
Solutions:
"Unknown" means the mail server didn't respond or blocked the verification attempt. This is not an EmailKit error
Try verifying the email again in a few hours — the mail server may have been temporarily down
Some mail servers aggressively block verification attempts. These emails will consistently return "Unknown"
"Unknown" results are still charged because the verification work was performed
Problem: You've set up a webhook but aren't receiving notifications.
Solutions:
Verify your webhook URL is correct and publicly accessible
Make sure your server is returning a 200 status code within a reasonable time
Check that you've subscribed to the right events (e.g., bulk.completed, verification.completed)
Test your endpoint by sending a manual POST request to confirm it's working
Check your server logs for incoming requests
Make sure your firewall isn't blocking requests from EmailKit's servers
Problem: The EmailKit dashboard isn't loading or showing errors.
Solutions:
Try refreshing the page
Clear your browser cache and cookies
Try a different browser or incognito mode
Check your internet connection
If the issue persists, check our status page or contact support
