email validation api key
Email validation API key
Create an API key, keep it server-side, and use it to authorize requests to the verification endpoints.
Keys are tied to an account and can be revoked.
Store them in environment variables, not in browser code.
Use separate keys for production and staging if you need isolation.
curl -X POST "https://your-domain.com/api/v1/verify?email=secure@example.com" \
-H "X-Api-Key: ev_your_key_here"
Can I expose the key in the browser?
No. Keep it on the server and proxy calls from your backend.
How many keys can I create?
The app supports multiple API keys per account.
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