Example
See a practical validation API request, response interpretation, and suppression policy for valid, invalid, risky, catch-all, and unknown addresses.
The simplest validation call accepts one email address and returns status, sub_status, confidence, provider evidence, and individual signals.
A practical product policy usually suppresses invalid and disposable addresses, segments catch-all and role addresses, and retries unknown results.
| Result | Policy | Reason |
|---|---|---|
| valid | Accept | Evidence suggests the mailbox is reachable. |
| invalid | Suppress | Hard failures damage reputation and waste sends. |
| risky | Segment | Risk depends on campaign and recipient context. |
| unknown | Retry or send conservatively | The provider did not produce reliable evidence. |