← All breaking-change reports

Twilio API breaking change: response-prop-removed on GET /v1/LinkShortening/Domains/{DomainSid}/Config

twilio · breaking · upstream source

What changed

According to the OpenAPI spec diff (twilio/twilio-messaging-1.40.0-to-1.49.0), the following surface changed:

response-prop-removed: GET /v1/LinkShortening/Domains/{DomainSid}/Config -> 200 messaging_service_sids

Who is affected

The DomainConfig response no longer carries the messaging_service_sids array.

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 DomainConfig response no longer carries the messaging_service_sids array. Code that read config.messaging_service_sids to learn which messaging services are attached to a domain must instead query the dedicated association surface. To resolve the domain for a known messaging service, call GET /v1/LinkShortening/MessagingServices/{MessagingServiceSid}/Domain. To manage or verify a specific pairing, use the /v1/LinkShortening/Domains/{DomainSid}/MessagingServices/{MessagingServiceSid} endpoint. There is no single call returning the full list of service SIDs for a domain, so callers that enumerated the array should iterate over their known messaging service SIDs and reverse-resolve each one.

Before:

const config = await fetchJson(`https://messaging.twilio.com/v1/LinkShortening/Domains/${domainSid}/Config`);
const sids = config.messaging_service_sids;

After:

const resp = await fetchJson(`https://messaging.twilio.com/v1/LinkShortening/MessagingServices/${messagingServiceSid}/Domain`);
const attached = resp.domain_sid === domainSid;

Replacement data source: GET /v1/LinkShortening/MessagingServices/{MessagingServiceSid}/Domain (reverse lookup) or the per-pair association endpoint under /v1/LinkShortening/Domains/{DomainSid}/MessagingServices/{MessagingServiceSid}.

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.