TumaFlow guides
WhatsApp API integration
Call TumaFlow from your billing engine, CRM, or mobile backend—enqueue messages, track outcomes, and verify webhooks with shared secrets.
Production integrations need predictable error semantics, idempotency keys, and retries that do not duplicate customer-facing side effects. TumaFlow’s API is designed around queued jobs so your services can POST a send request and poll or wait for asynchronous status.
Status callbacks and security
When delivery state changes, signed HTTP callbacks can notify your systems. Validate the signature using your workspace secret, reject replays where needed, and keep handlers fast so platforms do not disable endpoints for timeouts.
Templates still come from Meta
Your templates must be approved in Business Manager with the right language codes and categories. The API maps template names and components into Cloud API payloads the worker dispatches. Misclassified templates or missing parameter_name fields on named bodies will fail until corrected—plan for validation in CI if multiple teams edit copy.