API Behavior Changes
This page serves as notification about recent changes in API behavior following the upgrade to the
Webex Suite Meeting Platform.
If you encounter any of these issues, we kindly ask you to open a ticket with our support team. Our dedicated team will investigate the problem and provide you with the best course of action.
To provide further clarity, we would like to explain the most likely reasons behind these issues. As part of our ongoing efforts to enhance user experience and functionality, we have been gradually transitioning our customers to the
Webex Suite Meeting Platform throughout ’23 and ’24. This upgrade was communicated through newsletters and email outreach campaigns.
Webex Suite Meeting Platform is built upon the trusted and beloved Webex backend, with the meetings chat functionality powered by Webex Teams. However, due to the backend change, certain functional areas within the API have been affected. Here are the specific changes:
- Joining a
Webex Suite Meeting Platformmeeting via the join link now requires explicit login credentials and does not allow for assigning a host role through the link. We acknowledge that the previous implementation of the join link had flaws, and we are committed to resolving this issue by Q1 2024 CY. The new implementation will offer an improved and safer user experience.
- The meeting chat for compliance use cases can now be accessed through the events API. The
Webex Suite Meeting Platformleverages the robust Webex Teams chat functionality, which provides enhanced features such as meeting sharing to spaces and pre- and post-meeting huddles. Compliance officers can access chat data via the /events API, specifically the resource type
meetingMessages. If necessary, unwanted meetingMessages can be removed using the /meetingMessages API. It's important to note that meetingMessages are ephemeral unless configured otherwise in Control Hub. In the first half of 2024, we plan to introduce the ability to configure the persistence of direct messages (person to person).
QAare no longer available within meetings powered by the
Webex Suite Meeting Platform. Instead, the Sli.do embedded app must be used for this purpose. As a result, the meeting polls and QA API do not contain any data. To collect data about polls and QA, please open a TAC request access.
If necessary, we can temporarily revert your site to the previous backend until all the gaps have been addressed. If you require this option, please contact email@example.com, and your dedicated support representative will guide you through the process. To verify whether your system has been upgraded to the
Webex Suite Meeting Platform, you can perform a quick check using the instructions here.
Thank you for your understanding and patience as we work towards providing you with an improved API experience on the
Webex Suite Meeting Platform. If you have any further questions or concerns, please do not hesitate to reach out to us.