Configuring Twilio Webhooks for Linxi
Webhooks are what actually connect Twilio to Linxi — without them, a message can be delivered to your number by the carrier and Linxi will never know it happened.
What webhooks do
When someone texts your number, Twilio receives it first, then makes an HTTP request to a URL you configure, carrying the message content. That URL is Linxi's inbound webhook — it's how a text sent to your Twilio number ends up in your Linxi inbox. A second webhook (status callback) reports back delivery status for messages you send out.
The two URLs Linxi needs
Both should be set as HTTP POST, not GET.
Where to configure them
Two equivalent places, depending on your setup:
- Phone Numbers → your number → Configure → Messaging Configuration — sets it per-number
- Messaging Service → Integration → Webhooks — sets it for every number in that service at once, which is the more common setup once you're using a Messaging Service for A2P (see Messaging Service)
Testing it works
Send a real text message to your Twilio number from a personal phone. It should appear in your Linxi inbox within a few seconds. If it doesn't, see the troubleshooting steps below.
Troubleshooting
- Confirm the webhook URL is exactly
https://linxi.app/webhook/inbound, HTTP POST - Confirm the number's routing is Active, not Inactive, in the Twilio console
- Confirm the number is actually assigned to the Messaging Service you configured the webhook on
- Check that nothing else (an old webhook URL from a previous setup) is still configured directly on the number, overriding the Messaging Service's own setting