Go-live checklist

What to check before you put customers' WhatsApp numbers on your PipesBot App in production.

Run through this list before you onboard your first real customer. Each item links to the details.

  • Your App is on API v2. New Apps are. Legacy Apps can upgrade, one-way.
  • Your webhook verifies signatures and dedupes. Verify Standard Webhooks signatures on the raw body and skip repeated webhook-id values. See Webhook Security.
  • Your webhook URL is set before onboarding. number.onboarded is only sent to Apps with a webhook URL. Your handler stores numberId → customerId and is idempotent. See Know when they're done.
  • Inbound routing works. You find the customer from pipes.poolNumberId, tested with the example payloads.
  • Templates are approved on each customer's number before you send business-initiated messages. See Template Management.
  • A test send succeeded on a real customer number. Use Send a test message in Diagnostics.
  • You know which customers use Coexistence, and you turned on message echoes if you need messages sent from the phone. See Message echoes.
  • Number health is monitored. You poll the health endpoint and alert on failures. See Monitor number health.
  • You handle send errors. 429 RATE_LIMITED (60 requests/min per App key, shared by all your numbers: queue per customer, see Limits) and Meta's error 131062.
  • Customers have a payment method in Meta. See Who pays whom.
  • You have an offboarding procedure. See Offboard a customer.