Skip to Content
Wapitick developers

Go-live checklist

What to check before you switch from a test key to a live key.

  1. Live key, least privilege. Create a wk_live_ key with only the scopes you use, bound to one Business if you have several, with an IP allow-list for your servers. Keep it in a secret store, never in a browser or an app.
  2. WhatsApp number connected in Wapitick and in good quality; templates you send outside the 24-hour window are approved (GET /v1/templates).
  3. Consent. Only message people who agreed to hear from you; record it (contacts_record_consent) and honour STOP (contact.opted_out).
  4. Idempotency. Every write carries an Idempotency-Key (the SDKs do this). Retries never double-send.
  5. Webhooks. A live endpoint (test endpoints never get live events), signature verified on the raw body, answers within 10 s, de-duplicates on the event id.
  6. Errors. Handle 422 window_closed (send a template), 429 (wait Retry-After), 402 entitlement_required (plan), insufficient_balance (top up). See Errors.
  7. Limits. Check GET /v1/api-usage against api.requests_per_min and api.requests.day for your plan.
  8. Monitoring. Watch GET /v1/request-logs?status=error and the webhook delivery log for a week.

This page as Markdown