Platform DocumentationPlatform ChangelogAPI ReferencePush & In-App SDKsSDK Release Notes
Platform Changelog
FAQsWebsite
Back to All

Product Update - v6.16.0, March 2026

16 days ago

Webex Connect v6.16.0 release brings multiple new capabilities to help you continue delivering seamless customer experiences.

Summary

  • API for fetching Webex Connect Audit Logs

šŸ“˜

Release Date

The date of release will be communicated separately over an email.

Details

API for fetching Webex Connect Audit Logs

We are adding a new API to enable Webex Connect users to fetch Audit Logs for their tenants programmatically in a secure manner. This feature will be available in both AWS and Azure environments.
This API supports Oauth 2.0 based authentication and requires creation of a Service App in Webex Developer Portal (https://developer.webex.com/). For Webex Connect tenants that do not have a Webex Org ID assigned yet, there is an additional pre-requisite step of getting it generated by logging a request with your account manager. For more information, refer to the docs for Audit Logs API after this release.

Refer to the User Audit Logs API (v6.16.0 set) article in the Webex Connect API Reference.

Important Additional Notes:

  • Meta has announced an upcoming change to WhatsApp identity handling, with rollout expected to
    begin in June 2026. As part of this update, end users will be able to create and use a username in
    addition to their phone number and may initiate conversations with businesses using this username.
    When a user messages a business via username, their phone number will no longer be shared.
    Instead, businesses will receive a Business-Scoped User ID (BSUID), which serves as a unique
    identifier for interactions between the user and the business.
    In addition, Meta has introduced a Contact Book capability, available from March 16, 2026 and
    enabled by default for businesses. This feature stores mappings between phone numbers and
    BSUIDs for users who have previously interacted with a business. To help preserve phone number
    visibility and maintain conversation continuity, businesses must ensure that inbound or outbound
    interactions are maintained with existing customers between now and June 2026 so that these
    users are added to the Contact Book. This ensures that user identity mapping is retained when
    customers later reach out using usernames.
    Support for these changes is currently in progress in Webex Connect, including backward
    compatibility for existing services. More details and implementation guidance will be shared in
    subsequent releases.

Depcrecated Items

NA

Changelog

UpdateDescription
AddedAPI for fetching Webex Connect Audit Logs
FixedResolved an issue where the Watchtower report displayed an incorrect ā€˜Max TPSā€™ value.
FixedResolved an issue where users were unable to delete media files from the Media Manager if the uploaded filenames contained special characters. The system now allows users to remove these entries from the Media Manager.
FixedResolved an issue where deleted Export Logs Schedules were still being executed. [INC1382759]
FixedResolved an issue where email alerts about the expiry of scheduled Export Logs were being sent for schedules set to expire in 2039, instead of sending the alert seven days prior to the actual expiration date.
FixedResolved an issue where the Webex Connect API call for retrieving unread thread counts was returning an incorrect value for users, even when all threads had been read. The system now returns the accurate unread thread count, ensuring users no longer receive false notifications about unread messages.