bulk email verification api
Bulk email verification API
Upload or post thousands of emails and get structured results you can store, review, or pipe into another system.
Growth and Scale support larger batch jobs.
Results include status, score, disposable flag, and deliverability signals.
Use bulk mode for imports, customer hygiene, and campaign cleanup.
curl -X POST "https://your-domain.com/api/v1/verify/bulk" \
-H "X-Api-Key: ev_your_key_here" \
-H "Content-Type: application/json" \
-d '{"emails":["a@example.com","b@example.com"]}'
When should I use bulk mode?
When a list is too large for a form-by-form workflow and you need a batch result.
Can I mix file and API workflows?
Yes. Many teams validate signups one-by-one and clean historical lists in bulk.
Integration pattern
Use a server-side API key, validate on the backend, and return a short JSON result to your signup or import flow. That keeps secrets out of the browser and lets you enforce policy before you create user records.
Production concerns
The important pieces are rate limits, error codes, billing state, and clear response shapes. If a verification API is hard to integrate or hard to explain, developers will either skip it or wire it incorrectly.
FAQ
Fatal error: Uncaught TypeError: e(): Argument #1 ($s) must be of type string, null given, called in /var/www/emailverify/views/marketing/blog-post.php on line 33 and defined in /var/www/emailverify/app/helpers.php:82
Stack trace:
#0 /var/www/emailverify/views/marketing/blog-post.php(33): e()
#1 /var/www/emailverify/app/helpers.php(9): require('...')
#2 /var/www/emailverify/app/Controllers/BaseController.php(4): view()
#3 /var/www/emailverify/app/Controllers/MarketingController.php(59): BaseController->view()
#4 /var/www/emailverify/app/Router.php(32): MarketingController->blogPost()
#5 /var/www/emailverify/public/index.php(13): Router->dispatch()
#6 {main}
thrown in /var/www/emailverify/app/helpers.php on line 82