Choose a workflow
Decide whether the task needs an immediate individual result or a longer-running bulk job. Keep a clear separation between sample responses and actual checks.
Choose a workflow
Use an interactive check for one address only when the user can receive timely feedback. Use a background job for lists. Decide the destination fields before implementing the request.
Define the minimum record
Keep your internal record ID, original address, result category, reason, and check time. Store request references separately from user-facing labels.
Prepare for launch
Confirm the production base URL, authentication scheme, request limits, result schema, and charging policy. This documentation currently describes integration principles; it is not an executable API contract.
Before you enable this workflow
| Confirm | Why it matters |
|---|---|
| Production contract | Use documented fields, limits, and supported operations. |
| Failure policy | Decide what the application does when a check cannot complete. |
| Data boundaries | Keep credentials and customer data out of unnecessary logs. |