User Community Feedback

Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.

NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.

WebEx REST API: Allow cohosts to see Meeting Participant Details after meeting is over.

When we host virtual events and classes, we want to keep track of attendance based on the total duration of how long they are in the WebEx meeting. Currently once the class is over, the host has to manually export out a CSV and then import it into our internal application. By utilizing the API, we could fully automate this using the Meeting Participant Details endpoint. Currently, we could have each of our users authorize/integrate with WebEx API however, we would like also cohosts of meetings to have the same ability as hosts for that Meeting Participant Endpoint. From prior discussions with your development support team, it appears cohosts can only get that data DURING the meeting. Once the meeting is over, cohosts can no longer receive that participant data.


It would be great if there could be a new ability to allow cohosts to see Meeting Participant Details after a meeting is over.


The scenario we are envisioning is this:

  • User A creates a meeting and is the host.

  • User A adds User B as a cohost

  • User B integrates/authorizes a WebEx API system app via OAuth with a required scope if necessary.

  • User A will host and run the WebEx meeting

  • Once a day, on an automated schedule, User B, via the API, will look up all the meetings in the past 24 hours where it was a cohost and get the participant data, parse that data, and insert it into our internal database for tracking attendance.


Based on the security and privacy of the enterprise system, admin scopes are limited and that is another reason why we're requesting this feature specific to cohosts. Perhaps it's a new scope that has to be created for this feature to be implemented.


Thanks!



  • Francis
  • Dec 16 2022