New: MCP server monitoring is live. Start free
TwilioSchemaAdditive

New fields added in POST /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json (api.v2010.account.incoming_phone_number): [type]

Affected surface
POST /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json
Affected field
api.v2010.account.incoming_phone_number

What changed

New fields added in POST /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json (api.v2010.account.incoming_phone_number): [type] Affected surface: POST /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json. Root cause: schema `api.v2010.account.incoming_phone_number`. Detected at Thu, 05 Feb 2026 12:23:31 UTC UTC.

Diff

{
  "added_fields": [
    "type"
  ],
  "path": "POST /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json",
  "schema_path": "schema api.v2010.account.incoming_phone_number"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.