Verify Email

Verify the deliverability of an email address. This enrichment performs real-time email validation including syntax checks, mail server verification, and detection of disposable, role-based, and catch-all email addresses.

[!NOTE] See the API Guide for the shared request lifecycle (sync, async polling, async webhook), error envelope, rate limits, custom_vars, and deduplication. This page documents only the fields and behaviour unique to this endpoint.

Try it

Pricing

Endpoint

Input Parameters

Every enrichment also accepts the shared async, callback_url, and custom_vars parameters. See the API Guide for details.

Examples

Output Fields

Verification Code Values

The code field indicates the verification result:

Code	Status	Description	Recommended Action
5	Valid	Email is deliverable and safe to send	Safe to use
4	Risky	Catch-all/Accept-all domain	Use with caution
7	Risky	Unable to verify	Use with caution
1	Invalid	Invalid email syntax	Do not use
2	Invalid	Known spam trap	Do not use
3	Invalid	Disposable email address	Do not use
6	Invalid	Email will bounce	Do not use

Interpreting Results

Safe for Email Campaigns

Code 5 (Valid): Highest quality. Email is confirmed deliverable. Safe for all campaigns.

Use with Caution

Code 4 (Catch-all): The domain accepts all emails, so we cannot confirm this specific address exists. May still be valid.
Code 7 (Unknown): Verification inconclusive. The mail server did not provide a definitive answer.

Do Not Use

Codes 1, 2, 3, 6: These emails are invalid, spam traps, disposable, or will bounce. Sending to these addresses will harm your sender reputation.

Quality Ranking

For lead scoring purposes: Code 5 > Code 7 > Code 4. All other codes indicate unusable addresses.

Error Responses

Validation Error (422)

{
    "message": "The email field must be a valid email address.",
    "errors": {
        "email": ["The email field must be a valid email address."]
    }
}

Failed Enrichment (422 Unprocessable Entity)

When the enrichment fails, the HTTP status code is 422 and the response body contains "status": "failed" with an error_message:

{
    "id": 123,
    "type": "verify_email",
    "status": "failed",
    "input": {
        "email": "john.doe@example.com"
    },
    "output": null,
    "error_message": "Email verification service is temporarily unavailable"
}