← All breaking-change reports

Twilio API breaking change: response-prop-removed on POST /2010-04-01/Accounts/{AccountSid}/Calls/{Sid}.json

twilio · breaking · upstream source

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/{Sid}.json -> 200 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 scan --repo .

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

Pre-release. Change data is recorded from upstream provider releases, changelogs and OpenAPI spec diffs; every article links its source.