Twilio Changelog

We’re excited to announce that Group Texting is now generally available in Conversations! This feature allows businesses to create MMS conversations between multiple U.S. or Canada long code phone numbers and chat users, enabling more dynamic customer communications use cases. It’s great for sales, relationship management, and any scenario where multiple parties need to stay in the loop.

Additionally, this release includes a new Conversation with Participants API, which allows developers to create a conversation with up to 10 participants in a single API request. This streamlined approach helps Group Texting customers quickly initialize conversations, ensuring consistent and accurate group creation while avoiding potential duplicate group errors.

Checkout out our guide for Group Texting in Conversations to get started.

We previously announced in March 2024 that Twilio was going to End of Life (EOL) Twilio Video on December 5, 2026. After considering your feedback and our commitment to delivering personalized engagement, we’ve reversed our earlier decision to retire Twilio Video in 2026. Twilio Video will remain a standalone product as part of our customer engagement platform. 

Twilio Video will continue to play a key role in helping businesses provide trusted and personalized experiences. We’re also investing in enhancements to integrations with other Twilio channels, such as Voice, Messaging, and Twilio Flex, and new features to provide more actionable data-driven insights.

Current Twilio Video customers can continue to use Video as they always have; there’s no action or change needed. New Twilio Video customers can get started by reviewing our Video developer docs. 

A billing error has resulted in some accounts with Programmable Voice and/or Elastic SIP Trunking Calls Per Second (CPS) not being charged appropriately for the subscriptions on their account. The error has been addressed and proper billing of CPS subscriptions will resume as of October 21, 2024.

Twilio has identified and resolved an issue affecting the rate limits on several TaskRouter API endpoints. Due to a bug, rate limits were not being correctly enforced for the following TaskRouter endpoints:

• /Tasks?EvaluateTaskAttributes="foo=='bar'"    
  • Resource key: Task-List-EvaluateTaskAttributes
  • Limit: 3 requests per second (RPS)
• /Workers?TargetWorkersExpression="foo=='bar'"
  • Resource key: Worker-List-TargetWorkersExpression
  • Limit: 3 RPS
• /TaskQueues?EvaluateWorkerAttributes="foo=='bar'"
  • Resource key: TaskQueue-List-EvaluateWorkerAttributes
  • Limit: 3 RPS

Starting October 24, 2024, Twilio will reintroduce the rate limits for these endpoints. Any requests that exceed the specified rate limits will be throttled, and you may receive error code 429 if your usage surpasses these thresholds.

Note: This change does not impact customers who have previously requested and received exceptions to the default rate limits. We will continue to honor any existing exceptions.

For a complete list of TaskRouter API rate limits, navigate to TaskRouter > Workspaces in Twilio Console, click your workspace name, and then access the Limits page.

We're excited to announce the new Bundle Clone API, allowing developers to quickly duplicate approved regulatory bundles between accounts without the need to be re-approved.

With the Bundle Clone resource, developers can reuse compliance information across Twilio accounts. The resource creates a copy of a twilio-approved regulatory bundle against another account within the same organization. The new regulatory bundle is automatically set to the twilio-approved status, enabling you to start provisioning phone numbers in the new account immediately.

This is particularly useful for ISV customers that want to more quickly assign numbers to themselves, or customers that want to move resources between their accounts.

To enhance account security and prevent unauthorized hosting of phone numbers, Twilio now requires phone number ownership verification.

Between November 1, 2024, and January 5, 2025, Twilio will enter a Heightened Awareness Period (HAP) to help ensure reliable message delivery during peak traffic times, such as the U.S. presidential election, Black Friday and Cyber Monday.

Twilio will announce the End of Life (EOL) for Capability Tokens next year (2025). Please refer to our Capability Tokens Migration documentation on how to update your applications.

Upcoming EIN Requirement for US Short Code Campaigns

Starting October 15, 2024, the CTIA and US Short Code Registry will implement an enhanced vetting process for all new US Short Code campaigns. As part of this process, businesses will be required to submit a valid Employer Identification Number (EIN) during the onboarding phase. This change is designed to increase trust and security across the messaging ecosystem by ensuring a direct relationship between the brand and the short code campaign.

Additionally, starting January 15, 2025, the EIN requirement will apply to all short code renewals. Failure to provide the EIN within 60 days of renewal could result in short code suspension until the required information is submitted.

Key Dates to Note:

• October 15, 2024: EIN submission required for all new short code campaigns.

• January 15, 2025: EIN submission required for all short code renewals.

What You Need to Do:

• For new short code campaigns: Ensure you have a valid EIN ready to submit during onboarding after October 15, 2024.

• For existing short codes: Be prepared to provide your EIN when your short code comes up for renewal starting January 15, 2025.

For further details, please review the official CTIA guidelines and Twilio Short Code Onboarding Requirements.