An email verification API built for real traffic
Verify an address in the time it takes to submit a form. One GET request checks syntax, domain, mailbox and catch-all status, the API accepts 2,000 requests a second per account, and every result tells you why it came back the way it did.
What is an email verification API?
An email verification API checks whether an email address can receive mail, without sending one. You send an address and get back a result: deliverable, undeliverable, risky or unknown. MailVet also returns a reason code, the domain's mail server, a 0–100 score and flags for catch-all, disposable, role and free-provider addresses.
The difference is what happens on catch-all domains. Those servers accept every address, so most verification APIs stop and answer "accept-all" or "unknown". MailVet keeps checking and returns a definite deliverable or undeliverable verdict, in the same call. See /catch-all-email-verification for how that works.
One request, one answer you can branch on
Authenticate with a bearer key, pass the address, read result and reason. Full reference in /docs/verify.
curl "https://api.mailvet.app/v1/verify?email=dana.reyes@northwind.example" \
-H "Authorization: Bearer mv_live_…"{
"id": "vrf_01JD8X2T7Q",
"email": "dana.reyes@northwind.example",
"status": "done",
"result": "deliverable",
"reason": "catch_all_verified",
"score": 94,
"domain": "northwind.example",
"mx": "aspmx.l.google.com",
"flags": {
"catch_all_domain": true,
"disposable": false,
"role": false,
"free_provider": false
},
"credits_charged": 1,
"took_ms": 2140
}Published single-verify limit per account
Longest a call waits before handing back a pending id
Per email, catch-all checks included
Charged for an unknown result
What one call checks
Every check runs on every request. There are no add-ons to switch on and no second pass to pay for.
Syntax
RFC-valid address shape, typos in common domains, illegal characters. Caught before any network check, never charged.
Domain and MX
Does the domain exist and publish mail servers? We return the primary MX host so you can see who hosts the mailbox.
Mailbox
We talk to the receiving server the way a sender would and stop before any message is sent. Nothing reaches the inbox.
Accept-all domains
If the domain accepts everything, we run the deeper check and return catch_all_verified or catch_all_no_mailbox.
Disposable and role
Throwaway-inbox providers, role addresses like info@ and sales@, and free consumer providers are flagged on every result.
0–100 confidence
A single number for routing rules: accept above your threshold, review in between, reject below.
Published API limits, side by side
Most verifiers bury their rate limits or hand them out through sales. Ours is on the page, and the table includes the one competitor that publishes a higher number.
| Provider | Single-verify limit (published) | Catch-all verdict in the same call |
|---|---|---|
| MailVet | 2,000 per second | Yes, deliverable or undeliverable |
| ZeroBounce | ~8,000 per second (80,000 per 10 s) | No, a separate pass of up to 12 hours |
| Emailable | 25 per second | Accept-all check off by default |
| Bouncer | ~17 per second (1,000 per minute) | Separate deep catch-all check |
| Hunter | 10 per second | Only for some major providers |
| DeBounce | 5 concurrent calls | Deep check at 10 credits per address |
From each vendor's public API documentation, checked November 2026. Limits change; check the vendor's docs before you build on them. Ours are in /docs/rate-limits.
From sign-up to first verified address in two minutes
- 01
Create an account
100 free credits, no card. Your API key is on the first screen after sign-up.
- 02
Call /v1/verify
A GET request with the address. Most answers come back in a couple of seconds.
- 03
Branch on the result
Send on
deliverable, dropundeliverable, decide your own policy forrisky. Unknown is free. - 04
Let webhooks finish the rest
The rare check that needs minutes comes back as
pendingand lands on your webhook when done.
How the slow ones are handled
Most addresses verify in seconds. A small share of catch-all checks need longer, typically 1 to 6 minutes, because the receiving side has to be checked more carefully. The API never holds your request open that long: after 15 seconds it returns HTTP 202 with status: "pending" and an id.
You can poll GET /v1/verify/{id}, or set a webhook URL once and receive verification.completed events. Pending checks are not charged until they finish with a definite result. Details in /docs/webhooks.
Where teams plug it in
- ✓Signup and lead forms: reject typos and disposable inboxes before they reach your database
- ✓CRM sync: verify new contacts as they're created in HubSpot or Salesforce
- ✓Outbound tools: check every lead before it enters an Instantly, Smartlead or Lemlist sequence
- ✓Data pipelines: verify enrichment output in Clay, n8n or your own workers
- ✓Checkout and account creation: stop fake accounts at the door
- ×MailVet doesn't send email. It verifies addresses before you do.
- ×It doesn't find email addresses. Bring the address; we tell you if it's real.
- ×It doesn't sell, share or build lists from what you verify.
Email verification API questions
Is there a free email verification API?
Every MailVet account gets 100 free credits with no card, and they work on the API. After that it's $10 for 10,000 verifications on Starter, and unknown results are never charged.
How fast is the API?
Most verifications return in a few seconds. The account limit is 2,000 requests per second. A small share of catch-all checks take 1–6 minutes; those return a pending id after 15 seconds and finish by webhook or polling.
What does a catch-all result look like?
Instead of 'accept-all', you get a definite result: deliverable with reason catch_all_verified, or undeliverable with reason catch_all_no_mailbox. The catch_all_domain flag stays true so you can see the domain's setup.
Do you charge for unknown results?
No. If a mail server doesn't respond or a catch-all check can't reach a confident verdict, the result is unknown, the credit isn't used, and you can re-run it later.
Which languages are supported?
Any language that can make an HTTPS request. The docs have copy-paste examples for curl, Node.js, Python and PHP. The API is plain REST with JSON responses.
Do you send an email to verify the address?
No. Verification happens at the DNS and mail-server level and stops before any message is sent. The person behind the address never sees anything.
Is it GDPR friendly?
We process addresses only to verify them for you, never sell or share them, and delete bulk files automatically. A data processing agreement is published at /dpa.
Get a key and verify your first 100 addresses free
No card, no sales call. The key is on the first screen after sign-up.
Related
Last updated November 13, 2026