email verify api free
Email verify API free
There is no free tier on EmailVerify.se, but Starter is the entry plan and includes the core checks most teams need.
Starter includes syntax, MX, disposable, role-based, and JSON API access.
Upgrade only when you need bulk verification or SMTP probing.
A paid plan keeps abuse down and gives you predictable platform usage.
curl -X POST "https://your-domain.com/api/v1/verify?email=trial@example.com" \
-H "X-Api-Key: ev_your_key_here"
What if I need to test first?
Use the public demo and sandbox flows to see how the response shape works before subscribing.
Why no free tier?
Because abuse resistance, deliverability signals, and infrastructure checks cost real money to run.
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