/2010-04-01/Accounts/{}/Calls/{}/Feedback.json → endpoint removal
Twilio API
Stopped working
On December 31, 2023, the Voice Feedback API reached end-of-life and stopped working. Requests to the /2010-04-01/Accounts/{}/Calls/{}/Feedback.json endpoint fail after this date. The change also removed the Feedback widget in Console under call logs.
Calls it hits
/2010-04-01/Accounts/{}/Calls/{}/Feedback.json
What to use instead of these calls
Send call feedback with the Voice Insights Call Annotation API via POST insights.twilio.com/v1/Voice/{CallSid}/Annotation.
In Twilio API's words
Effective December 31, 2023, Twilio will end-of-life (EOL) the Voice Feedback API and the Feedback widget in Console under call logs.
Facts
- API
- Twilio API
api.twilio.com - Kind
- Endpoint removal
- Announced
- December 27, 2023
- Takes effect
- December 31, 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 /2010-04-01/Accounts/{}/Calls/{}/Feedback.json on Twilio API stopped working on December 31, 2023.
What happens to calls after December 31, 2023?
They have failed since December 31, 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 3
-
/2008-08-01/*Version retirement Stopped working -
/2010-04-01/Accounts/{}/Calls/FeedbackSummary*Endpoint removal Stopped working -
No date
POST /2010-04-01/Accounts/{}/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.