Choose the right method
| Real-time | Batch | |
|---|---|---|
| Use when | Validating at point of entry (form submission, CRM sync) | Cleaning a list of 10+ addresses |
| Endpoint | POST /v1/process-email | POST /v1/batch-process-email |
| Response | Immediate | Async — poll for status, then download results |
| Best for | Live enrichment, single lookups | Bulk list cleaning, pre-send scrubbing |
Verify a single email
Understand the response fields
| Field | Values | What it means |
|---|---|---|
deliverability | DELIVERABLE, UNDELIVERABLE, UNKNOWN | Whether the address accepts mail. Use DELIVERABLE for outbound sends. |
role | true / false | Role accounts (support@, info@, admin@) have lower engagement rates. Consider excluding from direct outreach. |
risk | LOW, MEDIUM, HIGH | Likelihood of bounce or spam trap. Filter to LOW for high-confidence sends. |
Process a batch
For lists of addresses, submit a batch job and poll until it completes.Poll for status
status is COMPLETED. Use a reasonable interval (e.g. every 5–10 seconds for small batches).Manage batch jobs
| Endpoint | What it does |
|---|---|
GET /v1/queued-process | List queued or in-progress batch jobs |
POST /v1/cancel-process | Cancel a job before it completes |
Next steps
Verify a single email
Full parameter and response reference for real-time verification.
Process emails in batch
Full reference for submitting and downloading batch jobs.
