Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Twilio connector page.How Event Streams is configured
No configuration is required in Twilio. StackOne creates a Sink and a Subscription for
each event type you enable, and removes them when you disconnect the account.
Do not edit or delete them in Twilio
They are listed under Monitor > Event Streams, with “StackOne” in the
description. Deleting one, or changing its destination, stops those events until
you reconnect the account.
Before you enable events
Two things determine whether the subscription can be created.
Confirm your region
Check the region of the Twilio account or API Key used on this connection. Event
Streams runs in US1 (United States) only, so a connection based in Ireland (IE1)
or Australia (AU1) cannot receive events.
Credentials used to create the subscription
StackOne uses the credentials already on the connection, so nothing further is
needed.
- Account SID and Auth Token — used directly.
- API Key — the Key SID and Secret are used, and the key must belong to US1.
- OAuth 2.0 — the access token is used. Twilio does not publish the scopes Event Streams requires, so if setup fails with a permissions error, review the Event Streams scopes granted to your OAuth application.
How events are delivered
Twilio delivers events in CloudEvents format, as a JSON array in which each element is
one event.
- Each event carries a unique
id, which you can use to discard duplicates. - Delivery is at-least-once, so an event may arrive more than once.
- Twilio retries a failed delivery for up to four hours.
- Twilio expects a response within five seconds and treats a slower reply as a failure.
- Events are sent from the Twilio IP ranges
35.90.102.128/25