<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Get encoded IDs from Webex client in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4640098#M1130</link>
    <description>&lt;P&gt;The Webex clients return the decoded space IDs, but the APIs are using the base64 encoded versions of the same.&amp;nbsp;&lt;SPAN&gt;Encoding the ID should work, but the region might be different in some cases. One way of doing it&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;If you would like the Webex clients to return the fully encoded space ID you can submit a feature request here&amp;nbsp;&lt;A href="https://ciscocollabcustomer.ideas.aha.io/" target="_blank"&gt;https://ciscocollabcustomer.ideas.aha.io/&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jun 2022 08:21:38 GMT</pubDate>
    <dc:creator>Janos Benyovszki</dc:creator>
    <dc:date>2022-06-28T08:21:38Z</dc:date>
    <item>
      <title>Get encoded IDs from Webex client</title>
      <link>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4640096#M1129</link>
      <description>&lt;P class="p1"&gt;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:&lt;/P&gt;
&lt;P class="p1"&gt;Space name: A funny Space&lt;/P&gt;
&lt;P class="p1"&gt;Space ID: a5b4f760-f329-22ec-ak4a-03puc5zz22b&lt;/P&gt;
&lt;P class="p1"&gt;Space URI:&lt;/P&gt;
&lt;P class="p1"&gt;Space URI (markdown): A funny Space&lt;/P&gt;
&lt;P class="p1"&gt;Participant count: 4&lt;/P&gt;
&lt;P class="p1"&gt;External participant count: 0&lt;/P&gt;
&lt;P class="p1"&gt;Conversation type: group&lt;/P&gt;
&lt;P class="p1"&gt;Actor role: Member&lt;/P&gt;
&lt;P class="p1"&gt;Space ID should reflect the proper room ID: Y2lzY29zcJKyazovL3VzL1JPT00vFHamMTNhNTAtYWVjYS0xMJVjLTg5ZWUtNTllYTcyMTG0YTA3&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 08:18:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4640096#M1129</guid>
      <dc:creator>Janos Benyovszki</dc:creator>
      <dc:date>2022-06-28T08:18:48Z</dc:date>
    </item>
    <item>
      <title>Re: Get encoded IDs from Webex client</title>
      <link>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4640098#M1130</link>
      <description>&lt;P&gt;The Webex clients return the decoded space IDs, but the APIs are using the base64 encoded versions of the same.&amp;nbsp;&lt;SPAN&gt;Encoding the ID should work, but the region might be different in some cases. One way of doing it&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;If you would like the Webex clients to return the fully encoded space ID you can submit a feature request here&amp;nbsp;&lt;A href="https://ciscocollabcustomer.ideas.aha.io/" target="_blank"&gt;https://ciscocollabcustomer.ideas.aha.io/&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 08:21:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4640098#M1130</guid>
      <dc:creator>Janos Benyovszki</dc:creator>
      <dc:date>2022-06-28T08:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: Get encoded IDs from Webex client</title>
      <link>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4666382#M1296</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/903055"&gt;@Janos Benyovszki&lt;/a&gt;, for clarification: is it always ciscospark://us/ or currently always?&lt;/P&gt;
&lt;P&gt;IIRC, there were plans to have there other localities as well in the future?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2022 11:51:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4666382#M1296</guid>
      <dc:creator>dtibbe</dc:creator>
      <dc:date>2022-08-09T11:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: Get encoded IDs from Webex client</title>
      <link>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4666420#M1298</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/922347"&gt;@dtibbe&lt;/a&gt;&amp;nbsp;good point. It is&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;currently always&lt;/STRONG&gt; , 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&amp;nbsp;ciscospark://us/ . Inside the org this prefix should not change though, so once you confirm it, it should be fine.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2022 12:45:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/get-encoded-ids-from-webex-client/m-p/4666420#M1298</guid>
      <dc:creator>Janos Benyovszki</dc:creator>
      <dc:date>2022-08-09T12:45:28Z</dc:date>
    </item>
  </channel>
</rss>

