DEVELOPER DOCUMENTATION

Handle one address deliberately

Validate the request format before sending it. A malformed request and an invalid verification result are different outcomes.

INTEGRATION NOTEBOOK
// Keep the evidence intact
verification
  outcome   → application decision
  reason    → review context
  checked_at → freshness

// Conceptual fields, not a live schema
Explore result handling ↗
MAILCHECKUP / DOCS / SINGLE-VERIFICATION↘

Interpret the result

Preserve the category, reason, and check time. A provider restriction should not become proof of an invalid mailbox.

Validate the request locally

Check required fields and supported address length before calling the service. Preserve the original user input so validation feedback does not force the person to start over.

Set an interaction budget

Define how long the form may wait and what happens after that limit. A timeout is a service condition, not a mailbox verdict. Offer an appropriate next step instead of silently dropping the submission.

Keep ownership confirmation

An address verification response does not prove the user controls the inbox. Use a separate confirmation workflow wherever ownership matters.

Before you enable this workflow

ConfirmWhy it matters
Production contractUse documented fields, limits, and supported operations.
Failure policyDecide what the application does when a check cannot complete.
Data boundariesKeep credentials and customer data out of unnecessary logs.