twilio-messaging-webhooks

Create a POST endpoint that reads form parameters like Body, From, and MessageSid, then return a TwiML MessagingResponse to reply or an empty response to acknowledge. Configure the webhook URL under your phone number's Messaging settings in the Twilio Console.

Use Twilio's RequestValidator in Python or validateRequest in Node.js with your auth token, the request URL, parameters, and the X-Twilio-Signature header. Return 403 Forbidden when validation fails to reject forged requests.

Yes, the same webhook pattern works across SMS, MMS, WhatsApp, and RCS. The difference is that WhatsApp and RCS webhook URLs are configured on the sender rather than the phone number, and From addresses use channel prefixes like whatsapp:+.

Pass a statusCallback URL when creating the message, then handle POST requests containing MessageSid, MessageStatus, and ErrorCode. Statuses flow from queued to sent to delivered, or undelivered and failed, and your handler should return HTTP 204.

Error 11200 means Twilio could not reach your webhook URL. Verify the endpoint is publicly accessible with curl, check DNS, firewall rules, and SSL certificate validity, and remember ngrok URLs change on restart.

Webhooks must respond within 15 seconds or Twilio retries, replies must use Content-Type text/xml with TwiML, and status callbacks are best-effort since delivered status requires carrier confirmation.