Email verification API and bulk list cleaning

Reduce bounces. Reach more of your customers.

Check new email addresses in real time, or reverify an existing list in bulk. Find undeliverable mailboxes, flag disposable addresses and catch likely typos before your next send.

Part of: Form verification Data cleansing Affiliate fraud detection Source audit

Try email verification free See a sample response from £0.006 per request, down to £0.002 at volume

Check addresses as customers enter them

Correct mistakes while the customer is still there, rather than losing the enquiry or the confirmation email.

Call the email verification API from your lead form, sign-up or checkout. Badly formed and undeliverable addresses are caught before they are stored, and a likely typo, such as gmial.com for gmail.com, can be shown to the customer to fix.

Check the email list you already have

Find out which addresses still work before your next campaign or database activation.

Upload your existing file to the bulk uploader and run email verification. Download the results to remove undeliverable addresses and review disposable, catch-all and role-based addresses separately. Provero has processed 1.4 million records in a single bulk upload.

Email data changes. Keep yours current.

People change jobs, companies close and old inboxes get abandoned. The record stays in your database, but the address may no longer work.

Take a customer database of six million email addresses as an example: even 1% becoming unusable means 60,000 wasted sends and contacts you can no longer reach.

“On average, at least 23% of an email list decays within just one year.”

ZeroBounce, Email List Decay Report for 2026.

The report analysed more than 11 billion email addresses checked during 2025.

“After 8 weeks, 2.3% (29/1278) of my sample was invalid.”

Ziemek Bućko, Hunter, How Often Should You Verify Your Mailing List (Email Data Decay), 4 November 2025.

Hunter rechecked 1,278 previously valid business email addresses weekly for eight weeks. A further 3.2% changed to accept-all, making their individual mailbox status harder to confirm.

Repeated bounces also damage the sending reputation your other emails depend on. Recheck your existing list before you put it back to work.

How to read the results

Result Meaning What to do
Not correctly formed Meaning: The address is badly formed, or the API rejects it as not a valid email address. What to do: Do not send to it. At capture, ask for the address again.
Deliverable, LOW risk Meaning: The mailbox check found the address deliverable and no flag applies. What to do: Keep it in your sending list.
Not deliverable Meaning: The mailbox check did not find the address deliverable. What to do: Remove it from your sending list. At capture, show any typo suggestion so the customer can correct it.
HIGH risk Meaning: The overall risk status is HIGH. What to do: Review it under your own acceptance and sending rules.
Catch-all Meaning: The domain accepts mail for any address, so the individual mailbox cannot be confirmed. What to do: Keep it out of the undeliverable group. Segment it and watch bounces.
Disposable Meaning: A temporary or disposable provider. What to do: Decide by context. A lasting address matters more for an account than for a one-off download.
Role-based Meaning: A shared inbox such as info@ or sales@ rather than one person. What to do: Often right for business contacts. Apply your own rules where you need a named person.
UNKNOWN risk Meaning: The risk status could not be determined. What to do: Treat it as unconfirmed rather than LOW risk.

A typo suggestion is for the customer to confirm. Do not overwrite a stored address with it without review.

API & bulk usage

The API and the bulk uploader return the same fields for every address. Email verification can also run alongside other checks in one Multi-validation request.

  • isSyntaxValid: whether the address is correctly formed.
  • isMailboxDeliverable: whether the mailbox check found it deliverable.
  • isCatchAll: whether the domain accepts mail for any address.
  • isDisposable: whether it comes from a temporary or disposable provider.
  • isRoleBased: whether it is a team or department address.
  • riskLevel: HIGH, MEDIUM, LOW or UNKNOWN.
  • typoSuggestion: a suggested alternative address that closely resembles the input.
  • checkResult: an optional result code, such as missingMX.

Email verification API example

POST https://api.provero.io/api/validate/email

Request (standalone email check)

{
  "email": "jane.smith@example.com"
}

Response (excerpt)

{
  "emailAddress": "jane.smith@example.com",
  "isSyntaxValid": true,
  "isMailboxDeliverable": true,
  "isCatchAll": false,
  "isDisposable": false,
  "isRoleBased": false,
  "riskLevel": "LOW"
}

Excerpt with an illustrative address and values, not the result of a live check. typoSuggestion and the optional checkResult code are left out. In a Multi-validation request to POST /api/validate/multiple, send the address as {"email": {"email": "jane.smith@example.com"}}; the result comes back in its own email block.

View the email API documentation →

Pricing

from £0.006 per request, down to £0.002 at volume

Requests / month Rate
0 – 5,000 £0.006
5,001 – 25,000 £0.00375
25,001 – 50,000 £0.00375
50,001 – 100,000 £0.003
100,001 – 200,000 £0.003
200,001 – 300,000 £0.0025
300,001 – 500,000 £0.0022
500,001+ £0.002

Paid from a prepaid balance that you can spend across any check. See current rates.

Need volume pricing? Email pricing@provero.io.

Related checks

No single check settles whether a record can be trusted. These are the ones people usually run alongside Email verification, each answering a different question about the same record.

See every Provero check →

Email verification FAQ

Can I check an existing email database?

Yes. Export the addresses from your CRM, email platform or database, upload the file to the bulk uploader and run email verification, then download the results to update your sending list.

Should I recheck a previously verified list?

Yes. An address that verified last year may not work now, because people change jobs and inboxes are abandoned. Recheck before a campaign, before bringing an older database back into use and as part of regular database maintenance.

Can I verify email addresses in bulk?

Yes. The bulk uploader checks a whole file and returns the same results as the API does for a single address.

Can I check addresses on a form?

Yes. Call POST /api/validate/email when the customer submits a sign-up, checkout or lead form. If typoSuggestion returns a likely correction, show it so the customer can fix the address before they leave.

What does a catch-all result mean?

The domain accepts mail for any address, so the mailbox check cannot confirm whether that particular mailbox exists. isCatchAll shows it. A catch-all address is unconfirmed rather than undeliverable, so keep it in its own group and watch bounces.

Does it flag disposable addresses?

Yes. isDisposable shows whether the address belongs to a temporary or disposable provider. Whether to accept one is your decision: it matters more for an account you expect to keep than for a one-off download.

Does a deliverable result confirm who owns the address?

No. It shows the mailbox can receive mail, not who controls it. A confirmation link or one-time code sent to the address checks that the person submitting it has access to it.

How much does email verification cost?

It starts at £0.006 per request and steps down to £0.002 at volume on a prepaid, graduated balance, with free credits to try it on a sample of your own data. Need volume pricing? Email pricing@provero.io.

Try email verification free

Create a free account and claim your credits, then check an existing file in the bulk uploader or call the API from your forms. No card required.

Create your free account