Skip to main content

Twilio Releases: Q2 2022

Welcome to Twilio’s Quarterly Release Webinar. In this developer webinar, you’ll get up to speed on all of Twilio’s latest product updates and take a behind-the-scenes look at new releases. Whether you’re just getting started with Twilio or are ready to go deep on new features, you’ll learn to build and deploy faster. In this fast-paced webinar, we’ll cover new features such as the Twilio Dev Phone, Twilio Pay, MMS for Long Text Messages, Alarms and so much more.

For the Japanese equivalent page, click here.

Q2 Release Webinar 2022

Changelog


Runtime Handler version 1.2.1 introduces access to headers and cookies for incoming requests to Twilio Functions through the new event.request object. Visit our documentation to learn more about this feature.

You can use this version today by setting @twilio/runtime-handler to use version 1.2.1

For new projects and those that don't specify a specific Runtime Handler version, we'll be rolling out version 1.2.1 over the coming weeks as the new default version.

Check out our docs to learn more about specifying which Runtime Handler version to use.


Programmable Voice

Generic Pay Connector now available in Public Beta Beta

The Generic Pay Connector is now available in Public Beta. The Generic Pay Connector is responsible for collecting sensitive payment information in a PCI compliant manner and passing it downstream to the payment processor of your choice - configured by you within the connector.

This connector supports 2 transaction types: charge and tokenization. The API provides flexibility to the payment processors to define the nature of the transaction taking place. 

With the release to Public Beta, a new generic endpoint “/” is available and the transaction type is now a method within the generic endpoint. With that, legacy endpoints - “/charge” and “/tokenize” available in the Generic Pay Connector are going to be deprecated in the next 30 days. Applications using legacy endpoints in private beta would need to be modified to consume from the root endpoint “/”.

With this release, there is also support for passing custom parameters in the request to the payment processor. These features are supported for both <Pay> verb and Agent Assisted Pay.

Learn more about this feature in our API docs.