Skip to main content
POST
Email Verifier
Email Verification OverviewYou input: Business or personal email addressYou get: Real-time deliverability status — valid, risky, invalid, or unknown
Unlike other Waterfall endpoints, this is synchronous — the result is returned immediately in the response. No job_id, no polling.

Status values

Business notes

Add your internal notes here — pricing, use cases, suppression logic, retry strategy for unknown, etc.
  • Billing: charged per verification call — unknown results are not billed
  • Catch-all domains: risky frequently indicates a catch-all domain, meaning the domain accepts all inbound mail without confirming individual mailboxes

Authorizations

x-api-key
string
header
required

To access the API, provide your API key in x-api-key.

Body

application/json

Verify Email payload. Requires a single email address and accepts optional custom_fields.

Request payload to verify a single email address.

email
string<email>
required

Professional or personal email address.

Required string length: 6 - 254
Example:

"john.doe@example.com"

custom_fields
object | null

Optional custom key-value metadata echoed on job input and output (useful for correlating internal source metadata). On create requests, omit the field or send JSON null when no custom fields are needed; both are stored as {}. When present, the value must be a JSON object with keys matching ^[A-Za-z0-9_-]+$ and values that are a string (max 1000 characters), number, or boolean. Empty string, arrays, and other non-object types return HTTP 400. On job GET responses, input.task.custom_fields is always an object ({} or populated).

Example:

Response

Email verification result returned immediately.

Verify Email response with status, input, and optional verified email output.

status
enum<string>
required

The status of the job.

Available options:
RUNNING,
SUCCEEDED,
FAILED,
TIMED_OUT,
ABORTED
Example:

"RUNNING"

start_date
string<date-time>
required

A date time in ISO 8601 format.

Example:

"2025-02-05T15:46:35.771751+00:00"

input
object
required
stop_date
string<date-time>

A date time in ISO 8601 format.

Example:

"2025-02-05T15:46:35.771751+00:00"

output
object