Twilio - Events
Twilio - Events
Twilio Events streams Twilio platform events (message delivery, call state changes, quota alerts) via a unified webhook bus — replacing scattered per-endpoint webhook configs.
Replaces scattered statusCallback URLs across resources
Does not replace inbound message webhooks (still configure SmsUrl on phone numbers)
POST /Sinks to create a webhook receiver, POST /Subscriptions to subscribe to event types and bind to the sink. Twilio asynchronously POSTs matching events to your URL.
Uptime · 30-day window
About this API
Events API (2021+) is Twilio's event bus, designed to replace per-product statusCallback configurations — separate webhook URLs on every phone number, Conversation, and Studio Flow created an operational nightmare. With Events, create an account-level Sink (pointing at your webhook URL), subscribe to event types (message.delivered, call.completed, limits.usage_threshold), and Twilio pushes all matching events to one place. Sink types also include Segment and AWS Kinesis for direct ingestion. Essential for monitoring, compliance audit, and CRM integration.
What you can build
- 1Centrally receive all Twilio events for monitoring/alerting
- 2Stream events into Kafka for downstream analytics
- 3Sync delivery status to CRM
- 4Get advance alerts as quotas approach limits
Strengths & limitations
Strengths
- Replaces scattered statusCallback URLs across resources
- Fine-grained subscription — subscribe to message.delivered without message.sent
- Event replay supported (up to 4 hours)
Limitations
- Does not replace inbound message webhooks (still configure SmsUrl on phone numbers)
- Sink events are lost if retries exhausted after failures
Example request
curl https://support.twilio.com/<endpoint>Getting started
POST /Sinks to create a webhook receiver, POST /Subscriptions to subscribe to event types and bind to the sink. Twilio asynchronously POSTs matching events to your URL.
FAQ
Can Events fully replace statusCallback?+
Inbound still needs statusCallback. Outbound state (sent/delivered/failed) can move entirely to Events.
Can I recover lost events?+
Within 4 hours, use the Replay API. Beyond that, rebuild from Twilio Insights or Bulk Exports.
Is there a delivery rate limit?+
Twilio rate-limits each sink to 100 events/s. Overage spills into the 4-hour replay queue.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST, Webhook
- SDKs
- python, javascript, java, ruby, php, csharp, go
- Response time
- 177 ms
- Last health check
- 5/12/2026, 7:38:32 AM
More from Twilio
Manage Twilio account credentials and hierarchy — create subaccounts, rotate auth tokens, and look up account metadata.
Twilio's core API for voice calls, SMS, Verify, and other programmable communications, billed per usage.
Twilio Autopilot is a sunset conversational-AI platform formerly used for IVR bots and NLU tasks (now superseded; migrate to Voice Intelligence or third-party LLMs).
Bulk-export Twilio usage history (Messages, Calls) as compressed daily JSON files — for audit, billing reconciliation, or data-warehouse ingestion.
Twilio Chat v1 is a sunset real-time chat SDK backend (superseded by Conversations). Existing projects still work; new projects should use Conversations API.
Twilio Content API centrally manages messaging templates across channels (WhatsApp/SMS/Messenger), including WhatsApp template approval flow and dynamic variable binding.
Twilio Conversations unifies multi-channel (SMS/MMS/WhatsApp/Chat/Email) messaging into a single "conversation" primitive with multi-participant, persistence, and read receipts.
Twilio Flex is a programmable contact-center platform for call centers — agent desktop, IVR/ACD routing, and deep integration with Twilio's full communications stack.