Twilio API breaking change: response-prop-removed on POST /2010-04-01/Accounts/{AccountSid}/Calls.json
What changed
According to the OpenAPI spec diff (twilio/twilio-api-1.20.0-to-1.30.0), the following surface changed:
response-prop-removed: POST /2010-04-01/Accounts/{AccountSid}/Calls.json -> 201 annotation
Who is affected
The annotation property is gone from Call responses and has no successor.
To find out whether your repo is hit — file and line number, no code leaving your machine:
npx mendapi sync # the one network call: fetch the change feed npx mendapi scan --repo . # local scan, nothing leaves your machine
How to fix it
Migration path:
The annotation property is gone from Call responses and has no successor. Reads of call.annotation now evaluate to undefined, so any logic branching on it is dead code. Delete the property reads and any downstream handling. If your application stored per-call notes in that field historically, move that data to your own datastore keyed by call SID; the API no longer round-trips it.
Before:
if (call.annotation) {
record.note = call.annotation;
}
After:
// annotation removed from the Call resource; per-call notes now live in the local datastore.
With your own LLM key configured (BYO compute — mendapi never proxies your credentials), npx mendapi llmfix turns this guide into a reviewable draft patch for your repo.
Detected and tracked by mendapi — Dependabot for every API you depend on. Scans run locally; your code never leaves your machine.
Related
- twilio breaking-change guide — every tracked twilio entry on one page, with fixability verdicts.
- 20 Twilio spec pairs: 358 findings from one engine, 142 from ours, and every disagreement named — the long-form methodology report behind this provider's tracked changes.
- All monitored providers — live change counts for twilio and 19 others.
- Migration pack catalog — every deterministic fix mendapi ships.
- Getting started — scan your repo in 30 seconds, no code leaves your machine.