API Documentation

VerifyAtlas Email Intelligence API

Call the first-party VerifyAtlas endpoint before account creation to detect disposable inboxes, role mailboxes, plus aliases, provider reputation, and signup risk signals.

Endpoint

Use this endpoint to check one email address at signup time.

POST https://api.verifyatlas.com/email

Send a full email address when available. Domain-only checks are supported when your workflow does not have the local mailbox value.

Authentication

Requests require your API key. Keep the key server-side and never expose it in production browser code.

Accept: application/json
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

Input Options

A full email address gives VerifyAtlas more signals to work with. The domain can identify disposable providers and corporate mail, while the local mailbox can add heuristics such as plus aliases, role inboxes, suspicious patterns, and input quality. Domain-only checks are useful for bulk screening or lead enrichment, but they cannot use those mailbox-level signals.

Option	Request shape	When to use it
Full email in JSON body	`{"email":"fake-user@mailinator.com"}`	Recommended for signup, login, trial, and account creation flows because it enables the strongest heuristics.
Full email as a query parameter	`↗email=fake-user%40mailinator.com`	Useful when your existing integration already passes identifiers through URL parameters.
Domain only in JSON body	`{"domain":"mailinator.com"}`	Useful when you only know the domain. Results focus on provider and domain risk, without mailbox-level checks.

Recommended Request

curl --request POST \
  --url "https://api.verifyatlas.com/email" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --data "{\"email\":\"fake-user@mailinator.com\"}"

Alternative Requests

curl --request POST \
  --url "https://api.verifyatlas.com/email↗email=fake-user%40mailinator.com" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --data "{}"

curl --request POST \
  --url "https://api.verifyatlas.com/email" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --data "{\"domain\":\"mailinator.com\"}"

Example Response

{
  "valid_input": true,
  "input": "fake-user@mailinator.com",
  "disposable_email": true,
  "confidence_level": 100,
  "corporate_mail": false,
  "verdict_reason": "temporary_email_provider",
  "popular_email_provider": false,
  "provider_name": "mailinator.com",
  "plus_alias": false,
  "role": false,
  "role_type": null
}

Response Fields

Field	Meaning
`valid_input`	Whether the submitted value looks like a valid email address.
`disposable_email`	Whether the domain is associated with temporary or throwaway inboxes.
`confidence_level`	Confidence score for the returned classification.
`corporate_mail`	Whether the email appears to use a business or organization domain.
`provider_name`	Detected email provider or domain.
`plus_alias`	Whether the address uses plus-addressing.
`role`	Whether the mailbox appears role-based, such as support or admin.
`role_type`	Role category when available.