The Notify API stops working
Twilio Notify API
Stopped working
Twilio will end of life the Notify API on December 31, 2025. After this date, calls to notify.twilio.com will fail. Twilio previously set this shutdown for April 25, 2024, but extended it to December 31, 2025.
What to use instead of these calls
Twilio retires Notify without a generally available replacement, as its push notifications API is a private beta. You must send push notifications through another push service such as FCM or APNs, or deliver SMS using the Messaging API endpoint POST /2010-04-01/Accounts/{}/Messages.json.
Twilio retires Notify without a generally available replacement; its push notifications API is a private beta.
In Twilio Notify API's words
We previously announced that the Notify product would end of life (EOL) on April 25, 2024. Notify will now EOL on December 31, 2025, in order for Twilio to provide an alternative solution for the current Notify product.
Facts
- API
- Twilio Notify API
notify.twilio.com - Kind
- Endpoint removal
- Announced
- January 23, 2024
- Takes effect
- December 31, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Twilio Notify API's own pages
Questions
When does this change take effect?
Calls to these calls on Twilio Notify API stopped working on December 31, 2025.
What happens to calls after December 31, 2025?
They have failed since December 31, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.