November 1, 2021 // Release Notes
Several new features and enhancements are now available in our API. Please be sure to review the information below regarding an upcoming breaking change to Call Flow Configuration updates and let us know if you have any questions.
1. Update Call Flow Configurations // Breaking Change - January 10, 2022
On January 10, 2022, we’ll change Update Call Flow Configurations to work like a proper PUT request.
This method currently works like a PATCH, where only parameters provided in the request-body are updated. After the change, this method will replace the entire Call Flow Configuration with the request-body, effectively removing parameters that are not provided. This change allows the user to remove parts of the Configuration, such as
callback_failover, without needing to delete the Configuration.
To use the new behavior in advance of January 10, 2022, append the parameter,
?future=now, to the PUT request path; it will be ignored after the update.
2. Transfer Array // Callback Request
A new transfer array has been added to callback requests to provide information on the status of the transfer-leg of your calls. If you use the
TRANSFER action in your call flow, details of the transfer-leg will be included in the body of
webhook callback requests. If multiple TRANSFERs are used in a single call flow, each attempt will have its own object within the array.
3. External ID and External Group ID // Make Call REST Request
Previously only available in Programmable Messaging, External IDs and External Group IDs are now supported in Programmable Voice as well. Include these parameters in the body of your Make Call requests to add user-defined IDs to a call or group of calls. IDs added to your requests are included in the call logs. Note: this feature has not yet been added to the DIAL call flow action.
1. Send Messages Batch // New Method
We’ve added a new API method POST
/Messages/Batch to support sending multiple SMS or MMS messages with a single API request. This method accepts an array of up to 100 unique message objects to allow your communications application to scale or handle bursts more efficiently. Use the
external_group_id parameter to apply a queryable id to each message sent in the request.
2. Group MMS // Send Message REST Request and Callback Request
Programmable Messaging now supports sending and receiving messages with multiple recipients. Turn any message into a Group MMS by replacing the
caller_no with an array of recipients in the new
group_nos parameter of the request body. The
group_nos property has also been added to the inbound message callback requests so your Voxology number can be included in a group message. Outbound Group MMS is supported in both the Send Message and Send Message Batch methods.
The Voxology Team