Event types lifecycle
Beta
Data Destinations is currently available as a Private Beta product and the information contained in this document is subject to change. Data Destinations is not a HIPAA Eligible Service or PCI compliant and should not be enabled in workflows that are subject to HIPAA or PCI. To learn more, see Private beta legal information.
The status of an event type determines how and if you can use the event type in Data Destinations. Event type status can be: available, deprecated, restricted, or discontinued. In most cases, Twilio deprecates an event type to give notice to users before an Twilio restricts or discontinues an event type.
Most event types have a status of available. If Twilio deprecated, restricted, or discontinued your event, then you'll get a warning in the Twilio Console.
Replace a deprecated or restricted event type with the recommended alternative before Twilio discontinues the event type.
Refer to the following resources to learn about important dates and alternatives when an event type status changes:
- The corresponding Twilio changelog entry
- The documentation for the event type
The following table shows what you can do with an event type based on the event type status.
| Event type status | Usage | Receive events in existing subscriptions | Create new subscriptions to the event type | Add the event type to existing subscriptions |
|---|---|---|---|---|
| Available | Available event types are ready to use. | Yes | Yes | Yes |
| Deprecated | You can still use deprecated event types, but start looking for alternatives. | Yes | Yes | Yes |
| Restricted | Immediately replace restricted event types with alternatives. | Yes | No | No |
| Discontinued | Twilio stops sending events for discontinued event types. If a subscription uses multiple event types, the subscription still receives events for event types that aren't discontinued. | No | No | No |