Treat bulk verification as a job

Longer work needs progress, completion states, and a stable job identifier when supported by the actual API.

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 / BULK-JOBS↘

Recover from interruptions

Avoid submitting a second copy of a large job simply because a browser refreshes. Follow the documented retry and idempotency contract.

Keep job and record state separate

A job can finish while some records remain inconclusive. Track submission, processing, and completion at job level, then retain each record’s result independently.

Recover without duplicating work

Persist the job reference before presenting progress. After a page refresh or network interruption, resume status checking rather than creating a second submission blindly.

Reconcile the output

Compare input, accepted, excluded, and result counts. Join results by stable identifiers where supported. Do not rely on row order unless the contract explicitly guarantees it.

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.