Email Verification API

Reach inboxes, not bounces, confirm an address is deliverable before you send.

Try it free from £0.006 per request, down to £0.002 at volume

What it checks

Email Verification confirms an address is genuinely usable before you send to it. It validates the syntax, checks whether the mailbox is deliverable, and surfaces the risk characteristics that drive bounces and spam complaints, disposable domains, role-based inboxes, catch-all servers and likely typos. It is the difference between a list that looks valid and a list that actually reaches people.

What it returns

Syntax valid , whether the address is correctly formed
Mailbox deliverable , whether the inbox can actually receive mail
Catch-all , whether the domain accepts mail for any address, which limits deliverability certainty
Disposable , whether the address belongs to a throwaway / temporary email provider
Role-based , whether it is a shared inbox such as info@ or sales@ rather than a person
Risk level , an overall low / medium / high read on the address
Typo suggestion , a corrected address where a likely misspelling is detected (e.g. gmial.com)

When to use it

At point of capture on sign-up, checkout and lead forms, to reject bad addresses before they enter your CRM.
Before an email campaign or send, to protect sender reputation and deliverability by removing bounces and spam traps.
Cleaning an existing list, where addresses decay over time as people change jobs and abandon inboxes.
Filtering lead-gen and form submissions, where disposable and role-based addresses are common quality and fraud signals.

When not to use it

As proof of identity, a deliverable inbox does not confirm who owns it. Combine with breach, IP fraud and name checks for that.
To make a hard accept/reject decision on catch-all domains, these can't be verified with certainty, so treat them as a caution, not a fail.
As your only fraud signal, disposable and role-based flags are useful inputs, but real fraud screening also needs IP and behavioural signals.
To repair a typo automatically without review, use the typo suggestion to prompt the user, not to silently rewrite their address.

How to read the result

Read deliverability and risk together, an address can be syntactically valid yet still risky to send to.

Deliverable, low risk: Safe to send. Syntax valid, mailbox reachable, no disposable or role-based flags.
Catch-all: Deliverability can't be confirmed because the domain accepts everything. Send with caution and watch engagement.
Disposable or role-based: Treat as low quality. Fine for transactional mail, risky for marketing and a useful fraud signal at sign-up.
Undeliverable or high risk: Suppress. Sending will bounce or harm your sender reputation; if a typo suggestion is present, prompt the user to correct it.

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

Prepaid balance, spent across any check. Each request is charged at the rate for the volume band reached, and earlier requests keep their lower rate. See full pricing.

Need custom pricing? pricing@provero.io

API & bulk usage

Run Email Verification as a real-time API call on every form submission, or upload a list for bulk cleaning before a send. Call it on its own, or combine it with other checks in a single request and get every signal back in one response.

Read the API reference →

Request

{
  "email": {
    "email": "simon@provero.io"
  }
}

Response

{
  "email": {
    "emailAddress": "simon@provero.io",
    "isSyntaxValid": true,
    "isMailboxDeliverable": true,
    "isCatchAll": false,
    "typoSuggestion": false,
    "isDisposable": false,
    "isRoleBased": false,
    "riskLevel": "LOW"
  }
}

Common Questions

Email Verification FAQ

Does Provero actually check the mailbox, or just the format?

Both. It validates syntax and then checks whether the mailbox is deliverable, and flags catch-all, disposable and role-based addresses, so you get real deliverability, not just a well-formed string.

What is a catch-all address and why does it matter?

A catch-all domain accepts mail for any address, so the server can't tell you whether a specific mailbox exists. Provero flags these as catch-all so you can treat them with caution rather than assume they're deliverable.

Will it catch disposable and temporary emails?

Yes. Disposable and throwaway providers are flagged, which is useful both for list quality and as a fraud signal at sign-up.

Can it suggest a fix for misspelled domains?

Where a likely typo is detected (for example gmial.com), the response includes a typo suggestion you can use to prompt the user to correct their address.

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 run a real sample of your own data through every check.

Start with this check

Create a free account, claim your credits and run Email Verification as a real-time API or a bulk upload. No card required.