Emver
Emver
Profiden+ Blog
Contact & Address

Email Verification API

Validate an email address without sending a message: syntax, domain and mailbox deliverability, disposable and role-address detection, and risk signals such as recently created or free-provider addresses. Keep bad addresses out of your candidate and customer records.

Response
Real-time
Inputs
1 required
Consent
Not required
Billing
Per successful call
POST /v1/email-verification
Sandbox · Production
  1. Your application sends

    • Email address*
  2. Profiden API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    Mail domain and mailbox checks

  4. You receive

    • Deliverable (yes/no/unknown)
    • Disposable or role address flag
    • Domain and provider type
    • Risk score
    • Suggested correction for typos
email-verification Full reference

What the Email Verification API does

Bounced invitations and disposable addresses quietly break onboarding. The Email Verification API checks that an address can receive mail, whether it is throwaway or a generic role address, and returns a risk score, so forms can correct mistakes on the spot and risky sign-ups can be reviewed.

It is a silent check: nothing is sent to the address.

Benefits of the Email Verification API

Check an email address is deliverable, not disposable and consistent with the person.

Fewer bounces

Invitations and reports reach real inboxes.

Disposable detection

Throwaway addresses are flagged at capture.

Typo correction

Suggests fixes for common domain misspellings.

Instant

Validate on blur in your forms.

Use cases

Email Verification API use cases

Where the Email Verification API is typically called, and what it settles there.

Candidate and client onboarding

Verify addresses before sending portal links.

Sign-up fraud control

Block disposable addresses on marketplaces.

Lead quality

Score inbound leads before sales follow-up.

CRM hygiene

Clean existing contact databases.

How the Email Verification API works

Request and response details, environments and a ready-to-import collection are in the developer console at console.profiden.com.

01

Authenticate

Call with your organisation API key. Sandbox and production use the same contract.

02

Send the inputs

Email address as a JSON body. Optional fields sharpen the match.

03

We verify at source

Profiden queries the authoritative record, normalises the answer and logs the request.

04

Act on the result

A verification status plus the fields listed above, in the same response envelope as every other API.

Built for the DPDP Act 2023

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

Encryption in transit and at rest
Data processed in India
Per-request audit trail
Masked identifiers in responses

Email Verification API: frequently asked questions

What teams ask before adding the Email Verification API to their integration.

No. The check is performed at the domain and mailbox level without sending a message.

Some mail servers accept all addresses or block verification. The response says so, and the risk score helps you decide.

Related APIs

APIs that usually run alongside the Email Verification API, on the same key.

All APIs

Get access to the Email Verification API

Tell us your use case and expected volume. We set up the organisation, share per-call pricing and issue keys.