Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Review your integration before live sending

Validate the complete path before rollout: application request → eligibility and funds → provider acceptance → delivery event → your application's update. Start with a controlled recipient and expand only after inspecting the results.

Credentials and configuration

  • Use the correct HTTPS application origin and API version.
  • Store named scoped keys server-side, with an expiry/rotation plan and no secrets in source control.
  • Confirm sending identity: verified email domain and sender, healthy WhatsApp channel, or approved SMS Sender ID.
  • Check allowance/wallet and provider capacity, including pending reservations.

Audience and content

  • Use valid destinations and stable customer identifiers.
  • Verify channel consent, unsubscribe and suppression behavior with a test excluded contact.
  • Preview template variables, missing values, email subject, From/Reply-To, and links.
  • Check campaign purpose, audience, timing, and timezone before launch.

Application reliability

  • Persist the request key before dispatch, reuse it for identical retries, and keep accepted batch IDs/references.
  • Handle partial acceptance and avoid resending accepted batch rows.
  • Honor rate limits and Retry-After instead of creating an uncontrolled retry loop.
  • Verify raw-body webhook signatures, persist events before acknowledging, and make downstream processing idempotent.
  • Distinguish accepted/queued from delivered in your product status display.

Automations and live checks

Run a simulation with representative data, review both condition outcomes and event timeouts, then inspect list restrictions, content, and sender readiness before publishing.
Perform a controlled live delivery check to an authorised recipient. Inspect actual delivery receipts, reply destination, message rendering, wallet/allowance result, and your webhook receiver. Simulation and API validation do not prove provider delivery.

Operational handover

Agree on who investigates failures and how to pause new work without duplicating in-flight messages. Ensure the deployment's background worker runs continuously. Preserve enough non-secret identifiers to reconcile uncertain sends and billing outcomes.
Next: bookmark troubleshooting, errors, and webhooks.
SMTP availability is deployment-dependent. Verify the shown gateway host and STARTTLS setup before moving an application to SMTP.