User Management with Control Hub

[Janos Benyovszki]

Use case:

A developer is using the XML API's

https://developer.cisco.com/docs/webex-xml-api-reference-guide/#!setuser/setuser to change Session/Meeting Types for Users to control Recording ability in a Site Admin managed site.

Question:

When the customer moves to being Control Hub managed, will the API continue to function the same, or will they need to account for this change in their application code/process?

[Janos Benyovszki · Accepted solution]

Control Hub user account management (create, update, delete) does require the use of the REST APIs. Once the site is migrated to Control Hub, they will have to start using the REST API for user management as well. Other functions of the XML API will still work.

[Anthony Holloway]

Thank you.  However, the current use case for the XML API is to set MeetingTypes for Users:

E.g.,

<meetingTypes>
    <meetingType>105</meetingType>
</meetingTypes>

What is the corresponding REST API and body content which will do the same?  Or, is this an instance, where the XML API will need to remain in use, due to the lack of parity between the two?

[Gasper A]

Hi Anthony, currently, it is not possible to assign meetingTypes via Rest. Rest now includes a new API list-meeting-session-types, used to retrieve meetingTypes assigned to a specific user, so I believe managing meetingType via Rest will be available in the near future. If your site migrates to CH, you should still be able to use the XML service to assign/manage sessionTypes.

[Anthony Holloway]

Thank you!