We have received reports of developers experiencing unexpected changes in API functionality, such as join links requiring login credentials and the meeting chats API not providing new results.

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.

The Webex Suite Meeting Platform is built upon the trusted and beloved Webex backend, with the meetings chat functionality powered by Webex. However, due to the backend change, certain functional areas within the API have been affected. Here are the specific changes:

• NEW meetingMessages in the /events API will soon show also direct messages ( private conversations between meeting attendees ) as well as messages exchanged in breakout sessions. Target release Feb/March 2025.
• NEW The Sli.do "Poll" and "QA" reports should be accessed via the Sli.do APIs. Documentation can be found for the US and EU with a different access point. A helpful FAQ is provided as well.
• Joining a Webex Suite Meeting Platform meeting 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 Q2 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 Platform leverages the robust Webex 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) and breakout session messages. meetingMessage events are only created for meetings on the new WSMP platform. Historical messages in meetings are not carried over.
• Meetings in spaces do work differently. When space meetings is desired, a Webex Meeting must be scheduled with a a roomid. Meetings are only loosely associated to spaces. This also means the room meetings info API won't work any longer and all meeting info should be collected from the meetings endpoint.
• Native polling and QA are 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.
• The enabledAnnotate field in the update or create a meeting API is not available for the Webex Meetings Suite. Other unavailable fields include: enabledAnnotate ,enabledSaveDocument, enabledPrintDocument,enabledAnnotate,enabledViewThumbnails,enabledRemoteControl,enabledViewAnyDocument,enabledViewAnyPage,enabledContactOperatorPrivately,enabledChatHost,enabledChatPresenter,enabledChatOtherParticipants
• The meeting transcripts endpoint will not have data for meetings where the Cisco AI Assistant is part of the meeting and instead the recording’s transcript transcriptionDownloadLink must be used. Some customers can access the new Cisco AI Assistant for meeting summaries and highlights. The Cisco AI assistant sounds similar to the legacy Webex Assistant but is based on a different technology. A meeting where the AI Assistant is enabled cannot also have the Webex Assistant enabled; they are mutually exclusive. The meeting transcripts endpoint is powered by the Webex Assistant, not the Cisco AI Assistant. This means that a meeting with the Cisco AI Assistant will not have any meeting transcripts from the meeting transcripts endpoint. Instead, the meeting transcript should be collected from the recordings REST resource, where a download link to the meeting transcript can be found. This transcript is known as the recordings transcript and is based on the same technology as the Webex Assistant-based transcript. Further information can be found here and here.

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 devsupport@webex.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.