Get encoded IDs from Webex client

[Janos Benyovszki]

Is Webex planning to update the "Copy Space Details" to show the actual room ID instead of the older method that has been deprecated? Makes tracking things with users difficult. Here's a redacted sample:

Space name: A funny Space

Space ID: a5b4f760-f329-22ec-ak4a-03puc5zz22b

Space URI:

Space URI (markdown): A funny Space

Participant count: 4

External participant count: 0

Conversation type: group

Actor role: Member

Space ID should reflect the proper room ID: Y2lzY29zcJKyazovL3VzL1JPT00vFHamMTNhNTAtYWVjYS0xMJVjLTg5ZWUtNTllYTcyMTG0YTA3

[dtibbe]

@Janos Benyovszki, for clarification: is it always ciscospark://us/ or currently always?

IIRC, there were plans to have there other localities as well in the future?

[Janos Benyovszki]

@dtibbe good point. It is currently always , based on my own testing and word from eng from earlier. This of course means, that it could change in the future, that's why I recommend starting with decoding a random room from your org to be sure your org is using ciscospark://us/ . Inside the org this prefix should not change though, so once you confirm it, it should be fine.

[Janos Benyovszki · Accepted solution]

The Webex clients return the decoded space IDs, but the APIs are using the base64 encoded versions of the same. Encoding the ID should work, but the region might be different in some cases. One way of doing it would be to decode the room ID of a random room from the org that the target space is located in and use the stem of it (ciscospark://us/) as a base and add the unencoded room ID to that. Region should not vary inside an org, so that should cover you for that case.

If you would like the Webex clients to return the fully encoded space ID you can submit a feature request here https://ciscocollabcustomer.ideas.aha.io/ .