You can now retrieve and delete Viber message templates via API, in addition to creating them.
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.
The Send message API reference now includes worked request examples for sending Viber template messages, covering both template categories: transactional templates and OTP templates.
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.
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.
The RCS guide previously described Rich Communication Services as "a protocol developed by Google." That was inaccurate, and it is now corrected.
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.
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.