email validation api json response

Email validation API JSON response

Use a predictable JSON structure to drive frontend validation messages and backend decision-making.

Fields map cleanly to validation rules and UI states.

Your app can block, warn, or allow based on the response.

The same shape works for single and bulk requests.

{
  "success": true,
  "email": "user@example.com",
  "result": "valid",
  "syntax_ok": true,
  "mx_found": true,
  "disposable": false
}

What should I store?

Store the result, score, and domain-level flags.

Can I inspect the raw output?

Yes. The response is structured so you can log or transform it safely.

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