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 39 of 39
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.
Get and Delete Viber template endpoints
You can now retrieve and delete Viber message templates via API, in addition to creating them.
Converse 2.0 API documentation, now at its own /converse section
Converse now has full API documentation, and its own top-level section on the developer portal — no longer nested under Connect.
Event Streaming migration guidance updated for general availability
The Event Streaming migration guide and overview no longer describe moving off the legacy Streaming API (SAPI) as optional. Existing customers are automatically migrated to the Pulsar-based Event Streaming service on a rolling schedule, with advance notice sent ahead of each migration.
Override the TURN relay region
You can now pin a meeting's TURN relay to a specific region using the experimental iceServers option on the JitsiMeetExternalAPI constructor. This is separate from pinning the meeting to a regional data center: that controls where the media bridge (JVB) lives, while iceServers controls which TURN relay a participant's…
outboundContent timing corrected on WhatsApp delivery receipts
The Delivery receipts for Outbound Messaging Apps(/connect/docs/delivery-receipts-for-outbound-chatapps) guide previously stated that the outboundContent object is attached to the receipt confirming delivery to the recipient (deliveredtorecipient). That was inaccurate.
Viber template send examples in the Send message reference
The Send message API reference now includes worked request examples for sending Viber template messages, covering both template categories: transactional templates and OTP templates.
RCS rich card media height documented as optional
The media.height field on RCS rich cards was documented as if a value were always required. It is now clarified as optional, defaulting to SHORT when omitted.
Event Streaming field reference corrected: JSON types are not fixed per field
The Event Streaming field reference previously said boolean values in events "are represented as strings... rather than native JSON booleans" — a claim its own example immediately contradicted by showing both a quoted and an unquoted boolean value in the same payload. The section has been corrected and expanded to desc…
Event Streaming timestamp field corrected: use interactionEventTS for event time
The Event Streaming field and event reference docs previously told integrators to use eventTS to calculate durations between lifecycle events — queue time, ring time, talk time, and wrap-up time. That was incorrect: eventTS is the time the interaction was first offered (queue entry), and it carries the identical value…
Prejoin page config option renamed
The Prejoin page guide(/jaas/docs/jaas-prefs-prejoin) now uses prejoinConfig.enabled in place of the retired prejoinPageEnabled option. The IFrame API checks each configOverwrite key against an allow-list and silently drops keys it doesn't recognize, so apps still setting prejoinPageEnabled: false were left with the pr…
Viber message templates
You can now create and manage Viber message templates — pre-approved message formats for transactional messages and OTPs, with dynamic {{parameter}} placeholders substituted at send time. Creating templates requires an admin role on the account.
alerting.rt scope clarified
The Real-Time Statistics documentation now spells out exactly what the alerting.rt metric counts and what it excludes, so it is interpreted consistently. This is a documentation clarification — there is no change to the metric's behaviour.
RCS attribution corrected
The RCS guide previously described Rich Communication Services as "a protocol developed by Google." That was inaccurate, and it is now corrected.
Actions & EventsStreaming
Bridge adapter endpoint for SAPI migration
The Streaming API migration guide now documents a backwards-compatible adapter (Bridge) endpoint — a second migration path for existing Streaming API integrations that cannot move to the Pulsar API directly.
templateId in Direct Send delivery receipts
WhatsApp delivery receipts now include a templateId field for messages sent via the WhatsApp Direct Send API, so you can correlate a receipt back to the exact template that was delivered.
LINE channel documentation
The full LINE channel documentation is now published. LINE is the most popular chat app in Japan, Thailand, and Taiwan, and it reaches users through the same 8x8 Messaging Apps API and webhook envelope you already use for SMS, WhatsApp, Viber, and RCS.
Actions & EventsWebChat
WebChat Content-Security-Policy guide
Embedding the 8x8 WebChat v2 widget behind a strict Content-Security-Policy meant guessing which directives to allow. A new Content Security Policy guide documents exactly what your embedding page's CSP needs.
Verification API templateKey parameter
The Verification API request now accepts a templateKey parameter, letting you select a pre-saved message template by its key instead of supplying the message content inline. The example values used across the Verification API documentation have also been standardised.
WhatsApp Automatic Events webhook
You can now receive WhatsApp Automatic Events webhooks — notifications sent when Meta detects a qualifying conversion event (a purchase or a lead) inside a WhatsApp thread that originated from a Click-to-WhatsApp ad. 8x8 forwards these detected events to your endpoint so you can feed conversion data into your own analy…
Work Analytics metrics and real-time report guides
The Work Analytics documentation now covers the full metric set for per-agent reporting, and the two guides that back the live agent and queue views have been published.
agentAverageTimeToAnswer metric
The agentAverageTimeToAnswer metric is now documented on the Work Analytics agent-activity endpoints. It is a timing metric, reported in seconds, and sits alongside the other agent timing metrics such as agentTotalTalkTime, averageTalkingInteractionsTime, averageOnHoldInteractionsTime, and averageWrapUpTime.
Business-Scoped User IDs (BSUID)
WhatsApp is rolling out optional usernames, which let people message a business without handing over their phone number. So that those users stay reachable, Meta gives every WhatsApp user a persistent Business-Scoped User ID (BSUID). 8x8 now surfaces the BSUID as user.channelUserId throughout the WhatsApp over 8x8 API.…
Outbound context on Outbound API v9
Outbound Messaging Apps delivery receipts on version 9 now carry additional context about the message they refer to. A new outboundContent object gives you a structured, channel-normalized copy of the WhatsApp message that was delivered, so you can reconcile a delivery receipt with the exact content sent without keepin…
Moobidesk renamed to Converse
The product previously known as Moobidesk is now called Converse throughout the developer documentation. All functionality is identical — only the product name has changed, so there is no API or behavioural change to act on.
Release 6869 meeting features
JaaS release 6869 adds a set of in-meeting improvements across subtitles, the whiteboard, and recording and transcription controls.
Contact Center Analytics release 2.14
The Contact Center Analytics documentation set has been refreshed for the 2.14 release.
WhatsApp Request Call Info
You can now check a customer's WhatsApp call permission status before you place a business-initiated call. Meta requires customers to explicitly grant permission before a business can call them on WhatsApp, and the new Get Call Permission Status endpoint tells you whether that permission is in place, whether you are cu…
Chat Apps inbound and outbound messaging
You can now follow end-to-end how-to documentation for sending and receiving Chat Apps messages on the 8x8 platform. The Chat Apps API lets you reach customers across supported channels — WhatsApp, Viber, RCS, LINE, and others — through a single message API, and receive their replies and delivery updates on the webhook…
Ring Group Management API update-members
The Ring Group Management API guide now documents a dedicated endpoint for targeted membership changes. Instead of reading a ring group, mutating its full member list, and writing the whole object back with PUT, you can send only the members that are changing.
API versioning header guidance corrected
We have corrected the API versioning guidance for the Administration API Suite to make clear which header carries the version on which kind of request.
Maestro SDK iframe microphone and speaker
When you embed the Maestro SDK in an <iframe, loading the URL on its own isn't enough to enable audio — modern browsers block microphone capture and speaker selection unless the embedding page explicitly grants them. The Maestro SDK overview now documents the allow attribute you need so that call and audio features wor…
Administration API Suite changelog
The Administration API Suite now has a dedicated changelog so you can track every change to the suite in one place, newest first. Whenever an API in the suite gains a new capability, changes behaviour, or has its documentation clarified, the change is recorded there.