real time email verification api
Real time email verification API
Call the API before you create an account so disposable addresses and bad syntax never make it into your database.
Optimized for form validation and user-facing flows.
Return a short JSON payload the frontend can display immediately.
Pair with client-side checks for a smoother signup experience.
curl -X POST "https://your-domain.com/api/v1/verify?email=signup@example.com" \
-H "X-Api-Key: ev_your_key_here"
Do I need JavaScript?
No. Any backend or edge function that can make HTTP requests can use the API.
Is it synchronous?
Yes. The response is immediate enough for user-facing signup validation.
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