Production-ready whatsapp, on day one.
The boring infrastructure — signing, retries, suppressions, webhook verification, audit — is done. Your code is one POST.
- Text messages through Meta Cloud API or 360dialog
- E.164 sender and recipient validation
- Threaded inbound conversations
- Signed provider webhook verification
- Retries for transient provider failures
- Per-recipient suppression handling
- Unified logs and message IDs
Senddio WhatsApp vs. direct BSP
What changes once you ship WhatsApp on Senddio.
WhatsApp — FAQ
The current sender supports Meta Cloud API and 360dialog. Add the provider credentials and phone-number ID in Channels before sending.
Send the channel, from and to numbers in E.164 format, a text body, and an optional tag. Template and media payloads are not part of the current public send contract.
Inbound WhatsApp messages are verified, stored and exposed as MESSAGE_RECEIVED events. Your application or agent can consume those events and send an allowed text reply through /v1/send.
Free includes 10 WhatsApp messages per month. Starter includes 100 and Pro includes 1,000. Eligible paid plans support metered overage; connected-provider charges and policies also apply.
Not through the current public /v1/send contract. The supported WhatsApp payload is text. Use your connected provider directly if you need media before Senddio exposes a documented media field.