apiPulse.app

Twilio

Twilio developer platform and API changelog updates

Twilio API Changelog Monitoring

Twilio platform changes may influence messaging, voice, identity, or event-driven integrations that need high reliability. This Twilio API Changelog Monitoring page is built to make changelog review easier so your team can manage update risk in communication systems.

Disciplined Twilio API Changelog Monitoring is important when messaging and voice systems are tied to customer communication and uptime expectations. It helps you review new entries quickly, understand the implementation impact, and keep communication workflows stable.

The benefit of Twilio API Changelog Monitoring is simple: your team gets a repeatable way to watch changes, evaluate risk, and act before small upstream updates turn into customer-facing bugs. Twilio developer platform and API changelog updates

Twilio API down?

Twilio API down? Soon we will add direct API status monitoring alongside Twilio API Changelog Monitoring. For now, go to the official API status page on the Twilio website. In the future, we plan to detect degraded service before the public status page is updated.

Recent changes

Showing the last 10 changes from this feed.

04-13-2026

Transit CallerID Sunset: Migrate to Verified CallerID or Immutable Call Forwarding Before May 31, 2026

Starting May 31, 2026, Twilio will begin sunsetting the Transit CallerID feature. Customers currently using Transit CallerID to present a different phone number than the one they're calling from will need to migrate to an alternative before this date.

Source
04-09-2026

Specify your SMS fallback sender when sending RCS messages

You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool. This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative. For more information, please see our docs.

Source
04-09-2026

Specify your SMS fallback sender when sending RCS messages

You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool. This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative. For more information, please see our docs.

Source
04-09-2026

AT&T phone numbers can now be added as RCS test devices

Twilio Programmable Messaging now supports adding AT&T test numbers to your RCS sender. You can now prototype and test your RCS sender on all major US carriers. Once you’re ready to use RCS for production traffic, submit your RCS compliance information and our operations team will guide you through the carrier approval process Go to Console to get started now. For more information, see our docs.

Source
04-09-2026

TCPA Known Litigators Check is now available in Compliance Toolkit

The TCPA Known Litigators Check is now available within Compliance Toolkit to help safeguard your messaging by identifying and blocking messages to phone numbers believed to be associated with individuals or entities with a history of filing TCPA-related legal actions.  This safeguard intelligently filters non-essential communications, such as marketing/promotional messages to phone numbers associated with known litigators, while allowing essential traffic, like transactional alerts, otp, and customer support messages, to reach the recipient.  When a message is blocked by this feature, Twilio will return Error Code 30640. Learn more about this feature and how to enable it in our documentation.

Source
04-09-2026

TCPA Known Litigators Check is now available in Compliance Toolkit

The TCPA Known Litigators Check is now available within Compliance Toolkit to help safeguard your messaging by identifying and blocking messages to phone numbers believed to be associated with individuals or entities with a history of filing TCPA-related legal actions.  This safeguard intelligently filters non-essential communications, such as marketing/promotional messages to phone numbers associated with known litigators, while allowing essential traffic, like transactional alerts, otp, and customer support messages, to reach the recipient.  When a message is blocked by this feature, Twilio will return Error Code 30640. Learn more about this feature and how to enable it in our documentation.

Source
04-09-2026

Consent Management API is in Public Beta

Consent Management API is now available globally in Public Beta, allowing you to programmatically sync, store, update, and manage end-user consent preferences across RCS, SMS, and MMS channels. This API acts as a centralized source of truth for managing consent preferences, enabling you to seamlessly integrate consent data from external systems like CRMs or web forms directly into Twilio. Note that consent states updated via this API for a given Messaging Service are automatically enforced across all three unified channels (RCS/SMS/MMS) to ensure compliance, without requiring any code changes. Learn more about this feature and how to enable it in our documentation.

Source
04-09-2026

ConversationRelay Payment Card Industry (PCI) Compliance

Twilio ConversationRelay now supports Payment Card Industry (PCI) compliant Voice workflows when configured with PCI-compliant TTS (text-to-speech) and STT (speech-to-text) providers. Please refer to Twilio's Responsibility Matrix to see a list of PCI-compliant TTS/STT vendors and for further information. To learn more about ConversationRelay please see the docs.

Source
04-09-2026

Consent Management API is in Public Beta

Consent Management API is now available globally in Public Beta, allowing you to programmatically sync, store, update, and manage end-user consent preferences across RCS, SMS, and MMS channels. This API acts as a centralized source of truth for managing consent preferences, enabling you to seamlessly integrate consent data from external systems like CRMs or web forms directly into Twilio. Note that consent states updated via this API for a given Messaging Service are automatically enforced across all three unified channels (RCS/SMS/MMS) to ensure compliance, without requiring any code changes. Learn more about this feature and how to enable it in our documentation.

Source
04-09-2026

AT&T phone numbers can now be added as RCS test devices

Twilio Programmable Messaging now supports adding AT&T test numbers to your RCS sender. You can now prototype and test your RCS sender on all major US carriers. Once you’re ready to use RCS for production traffic, submit your RCS compliance information and our operations team will guide you through the carrier approval process Go to Console to get started now. For more information, see our docs.

Source