© 2026 EmailAwesome. All rights reserved.
Claim & start
Route the record only after the check is complete. Pending requests, timeouts and errors belong in a separate review queue—not in the four final results below.
Status
What it means
Typical handling
Valid
The address passed the checks available at the time of verification.
Continue under your data policy. Verification does not establish consent or guarantee delivery.
Invalid
Address doesn't exist or the domain can't receive.
Suppress or flag the address once the check is complete.
Catch-all
Domain accepts anything, so the mailbox can't be confirmed.
Keep separate for review; the individual mailbox is not confirmed.
Unknown
No definitive answer, usually greylisting or rate limiting.
Keep for review or a controlled retry. Unknown results are not charged.
Manual cleanup works when the problem is a list. It fails when email data is moving through forms, products, CRMs, enrichment jobs and reports before anyone has time to inspect it.
Bad emails enter through forms, sync into CRMs, trigger automations, reach enrichment jobs and distort reporting. By the time someone notices, the address has touched several systems that now need correction, suppression or manual investigation.
Products, forms, CRM imports and background jobs check the address before it spreads, then use returned statuses to accept, block, flag, segment or review while the data is still close to the source.
In the asynchronous flow, the request returns pending and the completed result is sent to your configured webhook. Wait for completion before using the email result.
Zapier
Signup, checkout or any field where a person is waiting for an answer.
A developer, working against the API reference.
In your own code, fast enough to block a form submit.
API
Signup, checkout or any field where a person is waiting for an answer.
A developer, working against the API reference.
In your own code, fast enough to block a form submit.
Submit the check from your server and show a clear pending state. Set a waiting limit and a fallback; do not promise a completed result in the initial response.
Store the verification ID and process the callback, or retrieve the check by ID. Release the record to downstream automation only after completion and your policy checks.
Start verification when an address is submitted. Keep pending checks separate and use the completed result before triggering outreach or other downstream actions.
Check incoming addresses before activating CRM automations. Match each completed result to its source record and keep unresolved checks in a review queue.
Re-verify ageing records on a schedule, so the database doesn't decay quietly between campaigns.
When a lead submits your form, start the check on your server. Link the verification ID to the source record and keep your API key private.
Receive the completed result at your configured webhook, or retrieve the check by ID. Set a waiting limit and bounded retries; send failed or unresolved checks to review.
Match the final result to the lead, then apply your routing rules before outreach. Prevent repeated callbacks from creating duplicate actions. Valid verified emails are also saved to Contacts, where you can search and organize them into lists.
Create a validation, keep the record pending, then use the completed result in your workflow.
01 / REQUEST
Review the documented endpoint and how to authenticate your request. Use example data and placeholders in any code sample.
POST /api/validations/email_validation
x-api-key: YOUR_API_KEY
Content-Type: application/json
{
"email": "user@example.com",
"results_callback": {
"url": "https://example.com/webhooks/email-validation",
"method": "POST"
}
}INITIAL RESPONSE / 201 CREATED
{
"id": "validation_id",
"status": "PENDING"
}02 / CALLBACK
The example response starts in PENDING. Handle the completed result when the callback arrives and route the record according to its status.
{
"id": "validation_id",
"status": "COMPLETE",
"email_address": "user@example.com",
"email_address_status": "VALID"
}Read the email result only after processing is COMPLETE. A pending response is not a final verification result.
This example shows VALID. Handle INVALID, CATCH_ALL and UNKNOWN according to your workflow policy.
FAQs
Is the API only for developers?
Developers usually implement the API, but RevOps, growth, product, and CRM teams benefit because verification happens automatically where email data enters or moves.
What statuses should my app expect?
Track processing state separately from the email result. PENDING, IN-PROGRESS and FAILED are not completed verification results. Once processing is COMPLETE, route VALID, INVALID, CATCH_ALL or UNKNOWN according to your workflow policy. A pending response that contains UNKNOWN is not yet a final Unknown result.
How does asynchronous verification return the result?
The request returns pending. The completed verification result is sent to the webhook configured for that workflow. Valid verified emails are also saved to Contacts. Wait for processing to complete before using the result in downstream actions.
Where should developers use the API?
Common use cases include signup forms, demo requests, onboarding flows, CRM imports, enrichment jobs, internal tools, and scheduled hygiene workflows.
What is an email validation API?
An email validation API lets a product or workflow check email addresses programmatically instead of waiting for manual uploads, spreadsheet cleanup, or after-the-fact data repair.
USE CASE
Turn your authorized B2B records into a client delivery your team can explain. Verify addresses with EmailAwesome, then document sources, duplicates, coverage, and records that still need review.
01
Agree on the delivery rules
02
Verify and reconcile the list
03
Prepare the client handoff
Best for:
B2B lead list delivery