Verify Email
Legacy `{ valid, error, code }` contract. Prefer POST /api/v2/verify.
MethodPOST
/api/v2/emails/verifyPrefer POST /api/v2/verify or lumail.verify(). This path stays for existing lumail.emails.verify clients and still uses the same verification engine.
valid: false is still HTTP 200 with { error, code }. Transport / auth failures use { name, message, statusCode }.
Body Parameters
| Name | Type | Description |
|---|---|---|
email | string | Required. Address to check. |
Response Fields
| Field | Type | Description |
|---|---|---|
valid | boolean | Policy decision. |
error | string | Present when valid is false. |
code | string | Present when valid is false. |
suggestion | string | Corrected address when the domain looks like a typo. |
warnings | string[] | Soft warnings when present. |