Developers have reported unexpected changes in functionality, such as join links requiring authentication and the meeting chats API not returning new results.

If you encounter any of these issues, open a ticket with our support team so we can validate your environment and recommend the best path forward.

These changes are a byproduct of the ongoing migration of customer sites to the Webex Suite Meeting Platform (WSMP).

anchorWhat you should do

• If you’re using meetings join links for automation, validate the authentication requirements for your meeting type and site.
• If you rely on meeting chat content for compliance or DLP/CASB use cases, validate your /events consumption for meetingMessages.
• If you rely on meeting polls or Q&A reporting, plan to use Sli.do APIs.
• If you rely on meeting transcripts, validate whether Cisco AI Assistant is enabled for the meeting.

anchorSummary of API Behavior Changes

Availability of direct messages in the meetingMessages event

• NEW meetingMessages in the /events API will soon also show direct messages (private conversations between meeting attendees) as well as messages exchanged in breakout sessions.

Availability of Sli.do API for Poll and QA

• 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 different access points. A helpful FAQ is provided as well.

Meeting join links will need authentication and do not allow host role assignment

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

The Meetings Chat legacy API is replaced by the events API most commonly used by DLP/CASB vendors

• 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. 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 must be explicitly licensed through a new scheduling API call

• Meetings in spaces work differently. When a space meeting is desired, a Webex Meeting must be scheduled with a roomid. Meetings are only loosely associated with spaces. This also means the room meetings info API will no longer work, and all meeting info should be collected from the meetings endpoint.

Native QA and Poll is replaced by Sli.do functionality

• 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 for access.

Certain meeting preconfigurations are not available any longer

• 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, enabledViewThumbnails, enabledRemoteControl, enabledViewAnyDocument, enabledViewAnyPage, enabledContactOperatorPrivately, enabledChatHost, enabledChatPresenter, enabledChatOtherParticipants.

A note about meeting transcripts when AI Assistant is enabled in the meeting

• The meeting transcripts endpoints return transcripts for meetings where either Webex Assistant or Cisco AI Assistant is enabled.

anchorAbility to temporarily opt out of the Webex upgrade

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, see the Webex Help Center article "About the Webex Suite meeting platform".

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.