Release Notes
Every customer-visible change on the developer portal, across Connect, Converse, Video Interaction, APIs, Integration, Analytics, Actions & Events, JaaS, Tech Partner, Administration, and Resolve. Aggregated by month, or regroup by product area. Each entry links to the relevant documentation.
📌 Sharing the latest? This month's releases → is a stable link that always shows the newest month.
All products
All channels
Showing 49 of 49
ConnectSMS
MMS guide
Added a standalone MMS guide under Connect SMS, pulling together sending, receiving, and delivery receipts for MMS into one page. The underlying mediaUrls field and webhook behavior were already documented across the Send SMS, Inbound SMS, and Delivery Receipts reference pages — this guide is a single starting point th…
ConnectSMS
SMS Test Program (US) guide
Added a guide for prospective customers and partners who want to test SMS delivery to US mobile phones on the 8x8 CPaaS platform before signing up: how to opt in from your own mobile phone, what kinds of test messages you'll receive, and how to opt out.
Inbound MMS media on the inbound SMS webhook
When a user sends an MMS to one of your MMS-enabled US/Canada virtual numbers, the inbound SMS webhook (inboundmessagereceived) now includes a mediaUrls array with a link to each media file, alongside the message text in body. mediaUrls is omitted for plain SMS.
MMS media support on the Send SMS API
You can now send media (image, audio, video, etc.) along with an SMS as an MMS, by adding a mediaUrls field to your send request — up to 10 HTTPS URLs, each up to 4096 characters. MMS is currently supported for US/Canada destinations only; for other destinations mediaUrls is ignored and the message is sent as a plain S…
Converse Reporting API: queue and status filters, corrected field reference
Get conversations data can now be narrowed by queue and by conversation status, and the Reporting API reference has been corrected to match the API's actual behaviour.
Button replies in the inbound Messaging Apps webhook clarified
The inbound Messaging Apps webhook(/connect/docs/inbound-chatapps-message) page now explains how to tell which WhatsApp button a customer tapped, with sample payloads for both kinds of button.
WhatsApp Direct Send
A new guide documents Direct Send: you send utility message content directly, and WhatsApp matches it to an existing template or creates one for you. You don't need to create a template or wait for approval before the first send.
WhatsApp pricing: service messages and in-window Utility templates now charged
The WhatsApp docs now reflect Meta's pricing change effective October 1, 2026. Two kinds of message that were free inside an open 24-hour Customer Service Window (CSW) are now charged per delivered message.
outboundContent on SMS delivery receipts
SMS delivery receipts now document the outboundContent object — a structured copy of the original outbound message the receipt refers to. It lets you reconcile a delivery receipt with the exact content that was sent without keeping your own copy of the outbound payload.
WhatsApp Business Calling guides rewritten
The four WhatsApp Business Calling guides (overview, user-initiated, business-initiated, and scenarios) have been rewritten to match how calling is delivered on 8x8.
Cloud Storage Service guides and API reference revamped
The Cloud Storage Service guides and API reference have been reorganized and expanded, adding documentation for region discovery and archived-object restoration, and reordering both the guides and the reference navigation around them.
WhatsApp Business App Coexistence
A new guide documents Coexistence — connecting a phone number that's already active in the WhatsApp Business app to the WhatsApp Business Platform (Cloud API) through 8x8 Connect or the ChatApps API, so both keep working on the same number at once. Your team can keep answering 1:1 chats from the mobile app while 8x8 Co…
JVB video bridge port requirement corrected
The technical requirements & whitelists(/jaas/docs/technical-requirements-whitelists) page previously listed TCP port 443 as required for JVB video bridges. That was inaccurate — JVB media only requires UDP port 10000, and TCP 443 is not a valid destination port for it. The Video Bridges section has been corrected acco…
Correlation and batch IDs on the Callflows API
The Callflows API now accepts two optional top-level fields for tracking your own requests: clientRequestId and clientBatchId. Both are echoed back in the Voice Session Summary (VSS) webhook, so you can correlate a webhook back to the request that created it, or to the batch it belongs to, without keeping your own mapp…
Webhook and callback URL sample values updated to HTTPS
Sample URL values across the SMS and Business Messaging (Chat Apps) API documentation — webhook configuration, dlrCallbackUrl, delivery-receipt callback overrides, and rich-content URL fields — now use https://example.com instead of http://example.com, so the examples no longer read as an endorsement of plain HTTP for…
Viber Template Status Webhook
You can now receive a Viber Template Status Webhook when Viber moderates a message template you registered, so your systems stay in sync without polling.