XML API 11.0.0 SP7 Release Notes
- Overview
- XML API support for machine account access for service-to-service calling
- GetSessionInfo: Tollfree numbers not available if toll-only enabled
- LstRecording SQL default time range of 4 weeks
- LstmeetingusageHistory returns timezone in String type
Overview
This release note describes the changes made in the release of Webex XML API 11.0.0 SP7. These changes apply to your integration with WBS 32.All features are backward compatible with existing integrations. There are changes to the latest schema definitions explained below.
XML API support for machine account access for service-to-service calling
Note: The feature is only for WBS31 (XML API v11.0.0).
Inside of Webex and Cisco components, the XML API now provides a new way to sign in with the CI access token for both user and machine accounts, only for service-to-service calling. This new support is provided by the new element accessToken, the CI access token in the sign in process.
XML API does not support service accounts due to security issues. Unless you require an account which needs user management for all customers, you should be using a machine account for service-to-service calling.
Affected APIs
securityType
High-Level Diagram
Schema Change
Sample Request
<?xml version="1.0" encoding="ISO-8859-1"?> <serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service"> <header> <securityContext> <siteName>Webex_Site_Name</siteName> <webExID>Webex_User_Account</webExID> <accessToken>CI_Access_Token which include Site and User Account information (Support CI User Token and CI Service Toekn)</accessToken> </securityContext> </header> <body> <bodyContent xsi:type="java:com.webex.service.binding.user.SetUser"> <webExId>Webex_User_ID</webExId> <privilege> ... </privilege> </bodyContent> </body> </serv:message>
Known Issues
None
GetSessionInfo: Tollfree numbers not available if toll-only enabled
Previously, the GetSessionInfo API response included all the global call-in numbers regardless of whether only toll, or both toll and toll-free options were selected in the audio privileges. With this change, we now only display the global call-in numbers corresponding to the audio privileges selected. For example, only toll global call-in numbers are displayed if toll only is selected as the audio privilege, and all the global call-in numbers are displayed if the toll and toll-free option is selected.
APIs impacted
GetSessionInfo
Example
When "toll only" is selected:
Previous functionality:
New functionality:
Known Issues
None
LstRecording SQL default time range of 4 weeks
Note: The feature is only for WBS32 (XML API v11.0.0).
The LstRecording SQL applies a default time range of 4 weeks if no time scope is specified. This is to fix an issue of DB time outs related with NBR/Service recordings.
If no time scope for calling the LstRecording API is indicated, the XML API system sets a default time of 4 weeks (28 days from the call time).
If the time scope indicated is more than 28 days in the XML request, an exception occurs with the message, “Maximum querying date range is 28 days”.
Affected XML APIs
LstRecordingKnown Issues
None
LstmeetingusageHistory returns timezone in String type
This schema change is to address the bug where the LstmeetingusageHistory API would not return the timezone attribute for the meeting with timezoneID > 61.
Previously, timezone was returned as an object defined by the schema, which used hard-coded mapping methodology that only supported timezoneID values from 0 - 61.
Now, both the timezoneID(int) and timezone description(string) are queried from the DB, so it so it no longer depends on a schema check.
Note: This schema change is for both WBS31 and WBS32.
Affected XML APIs
LstmeetingusageHistoryKnown Issues
None
Related Release Information
The XML API schemas and release notes are available at the Cisco Webex Developer Portal:
https://developer.cisco.com/site/collaboration/webex/webex-developer/develop-test/xml-api/reference/
The URL API release notes are available at the Cisco Webex Developer Portal:
https://developer.cisco.com/site/collaboration/webex/webex-developer/develop-test/url-api/reference/