Email Verification API
An email verification API lets your application ask one question — "is this address real?" — and get a structured answer back in milliseconds. Instead of building your own MX lookups and SMTP probes, you call an endpoint and read a JSON response.
What an email verification API does
Behind a single endpoint, a good verification API runs the full pipeline:
- Syntax and format validation
- DNS and MX record checks
- SMTP mailbox probing
- Disposable and role-address detection
- Catch-all domain detection
Each layer produces a signal, and the API bundles those signals into one response so you do not have to assemble or interpret them yourself.
Why validate at the point of capture
The moment a user submits an email address is the moment that address is cheapest to fix. Once a bad address is in your database, every downstream system — your CRM, your marketing tool, your billing records — inherits it.
Validating at the point of capture means:
- Fewer bounces — the address is checked before it is ever used to send.
- Cleaner data — a typo becomes a "please check your email" message instead of a silent record.
- Less cleanup later — you stop importing the problem and then paying to remove it.
This is why point-of-capture verification is the highest-leverage place to use an API, even before you think about cleaning old lists.
One JSON response, every signal
The API returns a single, predictable JSON object. For each address you get a verdict, a numeric score, and a reason code that tells you what failed — syntax, no MX, disposable domain, role account, or catch-all.
Because the reason is explicit, your application can respond intelligently: block a disposable address outright, flag a role address for review, and let a catch-all through with a warning. You are not stuck with a binary accept/reject you cannot tune.
Verdict, score and reason codes
- Verdict — the overall pass/fail result for the address.
- Score — a confidence number, so you can set your own threshold for borderline cases.
- Reason — the specific cause of a failure, returned as a code your code can branch on.
Using the score instead of the raw verdict is the difference between a hard rule and a policy. A 62/100 and a 5/100 are both "fails" on a naive check, but they deserve very different handling.
Getting started
Authentication is a simple API key sent in the request header. The verification endpoint accepts an email address and returns the JSON result described above. An illustrative example — replace api.multivalidator.io with your live endpoint — looks like this:
curl https://api.multivalidator.io/v1/verify/email \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "email=user@example.com"The API documentation covers the full request and response schema, rate limits, bulk jobs and webhooks, with samples in curl, JavaScript and Python.
Pricing and the free tier
MultiValidator is pay-as-you-go, so you only pay for the checks you run. See the pricing page for per-check pricing, bulk discounts and free-tier details.
Related reading
- Email verification vs validation — what "verification" means next to a plain format check.
- How to verify an email list — applying the same checks to a whole list.
FAQ
How fast is a verification request? Latency depends on the network checks involved — a simple syntax check is near-instant, while a full SMTP probe takes longer. The API returns every signal it can and lets the deeper checks complete where they add confidence.
Does the API support bulk? Yes. You can submit a list as a queued job and poll for the result, rather than firing one request per address.
What happens if a domain is temporarily unreachable? The API reports what it could not confirm rather than guessing. A mailbox probe that cannot connect is returned as unverified with a reason, not silently passed or failed.