What Twilio changed, 14 April 2026 to 6 October 2026
197 operations became 197. None were removed, 0 were newly deprecated, 0 were added, and 0 request fields became required.
Read from twilio/twilio-oai at d50069b and 157fb09 (version 1.0.0). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Twilio's published specification.
Twilio publishes one OpenAPI file per product in twilio/twilio-oai. This page reads twilio_api_v2010.json, the core REST API (api.twilio.com/2010-04-01: messages, calls, accounts and phone numbers), not the other product files. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
Nothing was removed in this window. That is a real result, not a gap in the check.
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.
Deprecated as of the current specification (0)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
No operation is currently marked deprecated.
Request fields removed from the specification
The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Twilio rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Twilio versions — see the note at the top of this page.
- POST /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Transcriptions.json no longer lists ConfigurationId (application/x-www-form-urlencoded)
Twilio API questions
Every answer below is computed from the snapshot above, and each links to the Twilio specification it was read from.
- Which Twilio API endpoints were removed recently?
- None between 14 April 2026 and 6 October 2026, in spec/json/twilio_api_v2010.json in twilio/twilio-oai. It went from 197 to 197 operations in that window, and every operation present at the start was still there at the end, at the same URL.
- Source: twilio/twilio-oai, the two commits compared
- Which Twilio API endpoints are deprecated?
- No operation in spec/json/twilio_api_v2010.json in twilio/twilio-oai, as of 6 October 2026, carries the deprecated flag. A specification can only show a deprecation the vendor marks in it, so Twilio's own changelog may still announce one.
- Source: twilio/twilio-oai, the two commits compared
- Did any Twilio API request fields become required?
- None between 14 April 2026 and 6 October 2026, among the JSON request bodies in spec/json/twilio_api_v2010.json in twilio/twilio-oai the comparison could read. A field inside a union (anyOf or oneOf) is not compared, so it is not counted either way.
- Source: twilio/twilio-oai, the two commits compared
- Where is the Twilio OpenAPI specification?
- In the twilio/twilio-oai repository on GitHub. This page reads spec/json/twilio_api_v2010.json at commit 157fb09 (version 1.0.0), dated 6 October 2026.
- Source: twilio/twilio-oai on GitHub
The Action does not check Twilio yet
It checks GitHub REST and Stripe. If you want your CI to check the Twilio endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.