Event Streams is an API that allows you to tap into a unified stream of every interaction sent or received on Twilio. With Event Streams, you can:
Stream your data to your existing systems by configuring a modern, persistent streaming technology like
. You can also send events to
Easily consume and leverage data from multiple Twilio products with consistent metadata, well-defined and versioned schemas, and control over which events you want delivered (starting with Messaging, Voice, and TaskRouter events, with all events coming soon).
Trust that your events will be queued if your system goes down and delivered as soon as it's back up, with event queuing for up to 4 hours.
Learn more about the API resources
Event Streams evolves event delivery at Twilio beyond a single-producer-to-single-consumer model, giving developers flexibility to stream events to multiple sinks.
To build with Event Streams, you'll use the following API resources:
— The various kinds of events that are accessible through the Event Streams APIs.
— The destinations to which the events you've subscribed to will be delivered.
— Subscribe to specific Twilio events and versions.
— Every Event Type has a Schema which defines how information is organized within events.
Event Streams is additive and will not replace existing webhooks. Twilio will continue to support and develop existing webhooks for TwiML use cases and for customers who prefer per-channel integrations.
Logging and retention
The maximum retention period for application logs through Event Streams will be seven days.
The maximum retention period for error logs will be 23 days at the account level.