email verification api
Email verification API
Validate syntax, MX, disposable domains, role-based addresses, and catch-all mailboxes before a user finishes signup.
Real-time JSON response for signup forms and backend workflows.
Disposable domain detection to block throwaway inboxes.
Bulk verification and webhook automation for larger pipelines.
curl -X POST "https://your-domain.com/api/v1/[email protected]" \
-H "X-Api-Key: ev_your_key_here"What it does
This API checks whether an address is structurally valid, whether its domain can receive mail, and whether the mailbox looks risky or disposable.
Why it matters
You keep your lists cleaner, reduce bounce rates, and stop fake signups before they hit your product.
Response example
{\n "success": true,\n "result": "valid",\n "disposable": false,\n "free_email": true,\n "score": 92\n}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
What is the fastest way to start?
Create a Starter subscription and call the verify endpoint from your signup form.
Does it support bulk files?
Yes. Growth and Scale support larger batch workflows.
Do these pages replace docs?
No. They support discovery, search intent, and onboarding.
Why keep the code example short?
Because developers need the shape of the request, not a wall of boilerplate.