APIs

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.

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…

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.

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.

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…

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.

You can now retrieve and delete Viber message templates via API, in addition to creating them.

The Send message API reference now includes worked request examples for sending Viber template messages, covering both template categories: transactional templates and OTP 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.

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.…

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…

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…