Twilio Notify reaches end of life on 2027-01-31
- Provider
- Twilio
- Endpoint
POST /v1/Services/{ServiceSid}/Notifications- Effective
- 2027-01-31
- Severity
- critical
- Change
- version-sunset
- Status
- verified
What changed
Twilio Notify (notify.twilio.com, e.g. POST /v1/Services/{ServiceSid}/Notifications) has been unsupported and closed to new customers since October 2022 and reaches end of life for existing customers on 2027-01-31, per Twilio's Help Center (superseding the 2025-12-31 date in the January 2024 changelog). Push sent through Verify, Voice, Conversations or Engage is not affected.
What to do
Move bulk SMS sends to the Messaging API (or Twilio's Bulk Messaging API) and push notifications to a direct APNs/FCM integration or another push provider, then remove Notify Services and Bindings.
Sources
- Provider notice (2024-01-23)
- https://help.twilio.com/articles/9198083260571-How-to-transition-off-Notify
- https://www.twilio.com/en-us/changelog/notify-api-eol-notice
- https://www.twilio.com/docs/notify/api/notification-resource
Check your code
bash
npx shapi-cli scan .shapi scan lists the call sites this change affects; shapi fix repairs them test-first when the advisory has an automatic fix. All advisories · Markdown · OSV · JSON