Updatesapi-twilio

Twilio API: API Changes (2026-02-05)

a14fdca9bd34 → 55a17be6f0f1Verified February 17, 2026

TL;DR

  • The Twilio API has added a non-success response with the status '408' to the /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Recordings/{Sid}.json endpoint.
  • An optional property 'incoming_phone_numbers/items/type' has been added to the response with the '200' status for the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json endpoint.
  • The /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json endpoint now includes an optional property 'type' in its '201' status response.
  • The /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json endpoint has been updated with an optional property 'type' in its '200' status response.
  • These changes aim to enhance the functionality and responsiveness of the Twilio API for developers working with call recordings and incoming phone numbers.

    • What Changed

  • Feature:

    • - Added a non-success response with the status '408' to the /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Recordings/{Sid}.json endpoint.

    - Added an optional property 'incoming_phone_numbers/items/type' to the response with the '200' status for the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json endpoint.

    - Added an optional property 'type' to the response with the '201' status for the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json endpoint.

    - Added an optional property 'type' to the response with the '200' status for the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json endpoint.

    Who's Impacted

    If you are currently using the /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Recordings/{Sid}.json endpoint, you may need to handle the new non-success response with the status '408'. If you are working with incoming phone numbers through the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json or /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json endpoints, you can now utilize the optional 'type' property for more detailed responses.

    Action Checklist

  • ☐ Review the updated API documentation for the /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Recordings/{Sid}.json endpoint.
  • ☐ Update your code to handle the new non-success response with the status '408'.
  • ☐ Test your application's interaction with the /2010-04-01/Accounts/{AccountSid}/Calls/{CallSid}/Recordings/{Sid}.json endpoint.
  • ☐ Familiarize yourself with the new optional property 'incoming_phone_numbers/items/type' in the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json endpoint's '200' status response.
  • ☐ Adjust your code to utilize the optional 'type' property in the '201' status response of the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json endpoint.
  • ☐ Update your handling of the /2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json endpoint to account for the optional 'type' property in its '200' status response.
  • ☐ Verify that your application correctly handles the updated responses from the Twilio API.
  • ☐ Consult the Twilio API documentation for any additional guidance on the updated endpoints.
  • ☐ Plan for potential future updates that may affect your application's interaction with the Twilio API.
  • ☐ Monitor your application's performance and adjust as necessary to ensure compatibility with the updated API.

    • Verification

    The information in this update brief is based on the following sources:

  • Commit 55a17be6f0f1: https://github.com/twilio/twilio-oai/commit/55a17be6f0f130e5d529f92c0bf774254bb0f1d1
  • Twilio API Spec Diff: https://github.com/twilio/twilio-oai/compare/a14fdca9bd34ae5ed5063d093f68fa4d9cf9b01f...55a17be6f0f130e5d529f92c0bf774254bb0f1d1

    • Last verified at: 2026-02-17T13:04:41.704004+00:00

    📎 Sources