Twilio API
/2008-08-01/* version retirement
Stopped workingSubscribe to Twilio APIShare
Twilio retired API version 2008-08-01 on December 15, 2023. The change affects calls to /2008-08-01/*. Following that date, requests sent to these endpoints fail with 404 responses.
Calls it hits
/2008-08-01/*
What to use instead of these calls
Switch to the 2010 version of Twilio API (2010-04-01).
In Twilio API's words
After December 15, 2023, any requests sent to Twilio’s 2008 API will fail with 404 responses.
Facts
- API
- Twilio API
api.twilio.com - Kind
- Version retirement
- Announced
- October 18, 2023
- Takes effect
- December 15, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Twilio API's own pages
Questions
When does this change take effect?
Calls to /2008-08-01/* on Twilio API stopped working on December 15, 2023.
What happens to calls after December 15, 2023?
They have failed since December 15, 2023.
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.
More from Twilio API 7
-
/2010-04-01/Accounts/{id}/Calls/{id}/Feedback.jsonRemoval Stopped working -
/2010-04-01/Accounts/{id}/Calls/FeedbackSummary*Removal Stopped working -
GET /2010-04-01/Accounts/{id}/Recordings/{id}/Transcriptions/{id}.csvEndpoint removal Stopped working -
GET /2010-04-01/Accounts/{id}/Recordings/{id}/Transcriptions/{id}.htmlEndpoint removal Stopped working -
GET /2010-04-01/Accounts/{id}/Transcriptions/{id}.csvEndpoint removal Stopped working -
GET /2010-04-01/Accounts/{id}/Transcriptions/{id}.htmlEndpoint removal Stopped working -
No date
POST /2010-04-01/Accounts/{id}/Messages.jsonBehaviour change Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.