Email Verification

Contact & Address

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

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.

Endpoint

POST https://app.emver.io/api/sandbox/v1/email-verification

Authorization: Bearer YOUR_API_KEY

Content-Type: application/json

Accept: application/json

Request parameters

Field	Type	Description
`email_address` required	string	Email address

Example request

cURL

curl -X POST https://app.emver.io/api/sandbox/v1/email-verification \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "email_address": "[email protected]"
}'

import requests

response = requests.post(
    "https://app.emver.io/api/sandbox/v1/email-verification",
    headers={
        "Authorization": "Bearer YOUR_API_KEY",
        "Accept": "application/json",
    },
    json={
        "email_address": "[email protected]"
    },
    timeout=60,
)
response.raise_for_status()
data = response.json()

const response = await fetch("https://app.emver.io/api/sandbox/v1/email-verification", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
    "Accept": "application/json",
  },
  body: JSON.stringify({
      "email_address": "[email protected]"
  }),
});

const data = await response.json();

$response = Http::withToken('YOUR_API_KEY')
    ->acceptJson()
    ->post('https://app.emver.io/api/sandbox/v1/email-verification', {
        "email_address": "[email protected]"
    });

$data = $response->json();

Replace YOUR_API_KEY and the placeholder values. Use the switch above to see production URLs.

Response

Structure · 200

{
  "status": INTEGER,
  "message": STRING,
  "data": {
    "deliverable": STRING,
    "disposable_or_role_address_flag": STRING,
    "domain_and_provider_type": STRING,
    "risk_score": STRING,
    "suggested_correction_for_typos": STRING
  }
}

Example · 200

{
  "status": 200,
  "message": "string",
  "data": {
    "deliverable": "string",
    "disposable_or_role_address_flag": "string",
    "domain_and_provider_type": "string",
    "risk_score": "string",
    "suggested_correction_for_typos": "string"
  }
}

Error · 4xx / 5xx

{
  "status": INTEGER,
  "message": STRING
}

See Errors & status codes for what each status means and which calls are billed.

About this API

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.

Typical uses

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.

Questions

Does it send an email to verify?: No. The check is performed at the domain and mailbox level without sending a message.
What does "unknown" deliverability mean?: Some mail servers accept all addresses or block verification. The response says so, and the risk score helps you decide.