Get and Delete Viber template endpoints
You can now retrieve and delete Viber message templates via API, in addition to creating them.
← All release notes
August 2026
16 updates shipped on the developer portal in August 2026.
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.
This page is a stable link — /release-notes/m/2026-08. Browse the full history in all release notes.