Email Deliverability & Fraud Validation
Credits: 1 per call.
Validates an email address for deliverability and risk. Returns the normalized address, deliverability verdict (deliverable, risky, undeliverable), a quality score (0–100), a toxicity score, and a set of boolean verdicts (isFree, isDisposable, isRoleAccount, isFull, isCatchAll, isToxic).
Use this endpoint at signup time to reject typos and disposable addresses before they enter your database, reducing bounce rates on transactional email and fraud signals from throwaway accounts.
riskLevel reference — standardized scoring you can branch on:
| Level | When |
|---|---|
NONE | Mailbox is deliverable and not flagged as disposable or toxic. |
MEDIUM | Domain is catch-all — accepts every address, so the specific mailbox cannot be confirmed to exist. |
HIGH | Deliverability is risky or unknown (e.g. mail server rejects probes), OR the domain belongs to a disposable / temporary email provider (Mailinator, 10minutemail, Guerrillamail, etc.). |
CRITICAL | Mailbox is undeliverable (does not exist or is full), OR the address scores above 40 on the toxicity index (associated with spam / abuse). |
The verdicts object always carries the underlying signals (isFree, isDisposable, isRoleAccount, isFull, isCatchAll, isToxic) so you can apply your own scoring on top if you need finer granularity.
Authorizations
Body
The email address to be validated.
"user@example.com"
Response
Validation results (Strict Envelope Pattern).
High-level outcome. OK means the request was successfully processed (regardless of business result). ERROR means the request was rejected or could not be processed.
OK, ERROR Stable result type code. Includes generic codes (SUCCESS, INVALID_REQUEST, UNAUTHORIZED, SERVICE_UNAVAILABLE, INTERNAL_ERROR, RATE_LIMIT_EXCEEDED) plus endpoint-specific result codes — see this endpoint's response examples.
Human-readable summary of the result. Always in English (per Language Conventions in the API overview).
Unique identifier of this request, generated by the API Gateway. Propagated end-to-end for traceability.
ISO 8601 datetime with Mexico City offset (-06:00). Always set by the API Gateway when the response leaves the system.
Whether this request will be charged against the client's plan. Typically true for successful business results and false for validation errors or system errors that prevented processing.
Response payload. null on error responses. Shape depends on the endpoint — see each operation's response schema.
Per-field error details. Present only on INVALID_REQUEST responses.