Objective
This article walks you through creating an Event Stream end to end: choosing and configuring the sink that receives your events, then creating the subscription that decides which event types are sent to it. You need both pieces before Twilio starts delivering event data.
Product
Event Streams
Environment
Twilio Console
Procedure
- In the Twilio Console, select Data in the left sidebar.
- Select Event Streams, then Sinks.
- Select Create Event Stream.
- You now see a two-task list: Select sink and Create subscription. The second task stays locked until the sink exists.
- On Select sink, select Add sink.
- On Select destination type, choose the type of destination you want to send events to. Use the Search destination types... box to narrow the list, select the destination you want, then continue.
- On Configure destination, enter a Sink name to help you identify this sink, then fill in the remaining connection and credential fields shown for the destination type you picked. The fields vary by destination type.
- On Review sink, check your entries. To change something, go back to the earlier step. Select Save to create the sink.
- You are returned to the task list with Select sink marked complete. On Create subscription, select Get started.
- On Select subscription events, enter a Subscription name to help you identify this subscription.
- Under Subscription events, select the event types to include. Events are grouped by product, use Search by product to find a group quickly, and expand a group to pick individual events.
- For each group you can leave Use latest schema version (recommended) on to always receive the newest schema, or turn it off and pin a specific Schema version per event.
- Select Details next to an event to see what that event contains before you include it.
- Select Finish. When the subscription is created you see a success confirmation and land on your sinks list, and Twilio begins delivering the selected events to your sink.
Additional Information
Events listed under Unsupported events cannot be added, because the destination type you chose does not support them. If a whole group shows no supported events, that destination type does not accept any events from that product.
Both the sink name and the subscription name are required, and a subscription must contain at least one event type, you cannot finish without them.
Sink creation and subscription creation are processed asynchronously. If the operation is still running when the page finishes, you see a message saying the data will reflect shortly; refresh the list a moment later to see the new record. If creation fails, you are taken back to the configuration step with the reason shown so you can correct it and retry.
This content was generated by AI and reviewed, edited, and verified by a human.