Skip to main content
InteraOne’s current WhatsApp strategy uses Twilio. It validates account credentials, sends through the Twilio Messages API, and receives form-encoded Twilio webhooks.

​
Required values

​
string
required
Internal channel name, 2–100 characters.
​
string
required
WhatsApp-enabled Twilio sender number.
​
string
required
Twilio Account SID.
​
string
required
Twilio Auth Token, stored by the gateway and masked in API responses.
​
string
Optional Twilio Messaging Service SID.

​
Setup

1

Prepare a Twilio WhatsApp sender

Complete Twilio’s WhatsApp onboarding and confirm the sender can exchange messages.
2

Create the InteraOne channel

Enter the values above in Dashboard → Channels → WhatsApp, then verify the credentials.
3

Configure inbound webhook

Point Twilio at https://YOUR_API_HOST/api/v1/channels/whatsapp/inbound/CHANNEL_ID using the HTTP method expected by the gateway.
4

Test both directions

Send from a real WhatsApp account and reply from the InteraOne inbox.
Inbound requests must include x-twilio-signature. The gateway reconstructs the request URL/parameters and validates the signature using the channel’s auth token before processing. Customer threads use whatsapp-<fromPhone> as their session key, are tagged whatsapp, and retain channel ID metadata for correct outbound routing.
If a reverse proxy changes the externally visible URL, signature verification can fail. Ensure PUBLIC_API_URL, Caddy host routing, and the Twilio webhook URL describe the same HTTPS endpoint.
Last modified on July 17, 2026