Cisco Webex Meetings API Updates Overview (API 42)

For more info on XML API 39 and XML API 11, see the Cisco Webex Meetings XML API Updates Overview (XML API 39 and Earlier).

For more info on XML API 40, see the Cisco Webex Meetings XML API Updates Overview (XML API 40 and Later).

For more info on XML API 41, see the Cisco Webex Meetings API Updates Overview (API 41).

For updates for XML API 11 SP9 and earlier, go to Cisco DevNet.

API 42.11.1 Updates

XML API 42.11.1 Updates

Click here to download the XML API 42.11.1 schema.

XMLAPI will `LstRecording` return as an extra field <`recordingUUID`>

Impacted APIs and Schema changes

LstRecording returns a new element recordingUUID for service recordings only.

This element has no returns in an NBR recording.

Schema changes

Affected APIs

LstRecording

Example API

Response of LstRecording

<ep:format>MP4</ep:format>    <ep:serviceType>MeetingCenter</ep:serviceType>    <ep:password></ep:password>    <ep:passwordReq>false</ep:passwordReq>    <ep:confID>239651171508160002</ep:confID>    <ep:recordingUUID>20679f82215f103bbcff005056a3e9b8</ep:recordingUUID>    <ep:shareToMe>false</ep:shareToMe></ep:recording>

API 42.11.0 Updates

There are no schema changes to the XML API 42.11.0 schema.

API 42.10.0 Updates

XML API 42.10.0 Updates

Click here to download the XML API 42.10.0 schema.

GetSessionInfo API returns a new node <registrationShortURL> that is available in the short-link format for Webex Events (classic) and Webex Trainings

Impacted APIs and Schema changes

Now almost all Webex URLs support the short-link format, but GetSessionInfo still returns the long-link format for registration URLs about Webex Events (classic) and Webex Trainings today. So we add new element naming <registrationShortURL> which is support the short-ling format for registration URL and keeps existing elements <registrationURL> for compatibility.

Schema changes

A new element <registrationShortURL> is added into GetSessionInfo response:

Affected APIs:

GetSessionInfo

Example API

registrationShortURL is returned for Webex Events (classic) and Webex Trainings

<ep:accessControl>
<ep:sessionPassword>plainPW</ep:sessionPassword>
<ep:listStatus>UNLISTED</ep:listStatus>
<ep:registration>true</ep:registration>
<ep:registrationURL>https://sqdemo6.dmz.webex.com/tc3300/trainingcenter/register/registerSession.do?siteurl=sqdemo6&confID=236703422899815816</ep:registrationURL>
<ep:registrationShortURL>https://sqdemo6.dmz.webex.com/sqdemo6/k2/j.php?MTID=t265bdc2ca9afd38c7d3cbed3e17974db</ep:registrationShortURL> //New element
<ep:passwordReq>true</ep:passwordReq>
<ep:registrationURLForMobile>https://sqdemo6.dmz.webex.com/tc3300/trainingcenter/meeting/sessionInfoMobile.do?siteurl=sqdemo6&confID=236703422899815816</ep:registrationURLForMobile>
<ep:registrationStatus>REGISTER</ep:registrationStatus>
<ep:isEnforceAudioPassword>false</ep:isEnforceAudioPassword>
<ep:isEnforceAudioLogin>false</ep:isEnforceAudioLogin>
</ep:accessControl>

API 42.9.2 Updates

XML API 42.9.2 Updates

Click here to download the XML API 42.9.2 schema.

XML API will block schedule classic Event after 2023/3/31

Impacted APIs and Schema changes

After March of 2023, if you call XML API: CreateEvent and SetEvent, shows the error message and code:

110065 After March of 2023, you are no longer able to schedulenor edit any new or existing Webex Events (classic). Refer to Webex Webinars ( https://developer.webex.com/docs/api/v1/meetings) to schedule events

Impacted APIs

CreateEvent
SetEvent

Schema changes

There are no schema changes.

Example API

XML API: CreateEvent

https://{sitename}.webex.com/WBXService/XMLService

request body:
<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
<securityContext>
<siteName>{sitename}</siteName>
<webExID>site admin account</webExID>
<password>xxxxx</password>
</securityContext>
</header>

<body>

<bodyContent xsi:type="java:com.webex.service.binding.event.CreateEvent">

<accessControl>

<sessionPassword>123aBc123</sessionPassword>

<enforcePassword />

</accessControl>

<metaData>

<sessionName>RetireECTest</sessionName>

</metaData>

<schedule>

<startDate>09/01/2023 14:29:15</startDate>

<openTime>15</openTime>

</schedule>

<remind>

<minutesAhead>10</minutesAhead>

</remind>

<panelists>

<panelistPassword>P@ss12345</panelistPassword>

<panelist>

<name>Test1 Space</name>

<email>aleyang3@malinator.com</email>

</panelist>

<panelist>

<name>Test2</name>

<email>aleyang4@malinator.com</email>

</panelist>

</panelists>

<attendees>

<attendee>

<name>Simon_3</name>

<email>aleyang5@malinator.com</email>

<sendReminder>true</sendReminder>

</attendee>

</attendees>



</bodyContent>

</body>

</serv:message>

Response:

<?xml version="1.0" encoding="UTF-8"?>

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">

<serv:header>

<serv:response>

<serv:result>FAILURE</serv:result>

<serv:reason>After March of 2023, you will no longer be able to schedule/edit any new/existing Webex Events (classic). Please refer to Webex Webinars (https://developer.webex.com/docs/api/v1/meetings) to schedule events</serv:reason>

<serv:gsbStatus>PRIMARY</serv:gsbStatus>

<serv:exceptionID>110065</serv:exceptionID>

</serv:response>

</serv:header>

<serv:body>

<serv:bodyContent/>

</serv:body>

</serv:message>

XML API: SetEvent

https://{sitename}.webex.com/WBXService/XMLService

request body:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<header>
<securityContext>
<siteName>{sitename}</siteName>
<webExID>site admin account</webExID>
<password>xxxxx</password>
</securityContext>
</header>
<body>
<bodyContent
xsi:type="java:com.webex.service.binding.event.SetEvent">
<event:sessionKey>17203097096</event:sessionKey>
<schedule>
<startDate>05/01/2023 14:29:15</startDate>
</schedule>
</bodyContent>
</body>
</serv:message>

Response:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
<serv:header>
<serv:response>
<serv:result>FAILURE</serv:result>
<serv:reason>After March of 2023, you will no longer be able to schedule/edit any new/existing Webex Events (classic). Please refer to Webex Webinars (https://developer.webex.com/docs/api/v1/meetings) to schedule events</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>110065</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>

API 42.9.0 Updates

There are no schema changes to the XML API 42.9.0 schema.

API 42.8.1 Updates

XML API 42.8.1 Updates

Click here to download the XML API 42.8.1 schema.

New XML API: SyncUser

Impacted APIs and Schema changes

New XML API: SyncUser support syncing user info from Control Hub to Webex Meeting system.

If your client hits rate limit, it will response "429 too many requests.", the afterRetry is 25 seconds in API response header.

If the user doesn't exist, it responds to error:" 000031 Control Hub managed user doesn't exist"

If your authentication doesn't have site admin privileges, it responds to error:"000031 Only Site Admin can call this API"

Schema changes

Example API

XML API: SyncUser

API 42.8.0 Updates

XML API 42.8.0 Updates

Click here to download the XML API 42.8.0 schema.

`GetLoginTicket` returns an extra node <webExID>

Impacted APIs and Schema changes

XML API: GetLoginTicket returns one extra node <webExID>

Schema changes

<xsd:complexType name="getLoginTicketResponse">
<xsd:complexContent>
<xsd:extension base="serv:bodyContentType">
<xsd:sequence>
<xsd:element name="ticket" type="xsd:string"/>
<xsd:element name="apiVersion" type="xsd:string"/>
<xsd:element name="webExID" type="xsd:string"/> -> new element
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

Affected APIs:

GetLoginTicket

API Sample:

GetLoginTicket

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<header>
<securityContext>
<siteName>sqci18</siteName>
<webExID>sqci18adm@mailinator.com</webExID>

<accessToken>MTxxxxxxxxx10bcc862be5</accessToken>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.GetLoginTicket">

</bodyContent>
</body>
</serv:message>

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:use="http://www.webex.com/schemas/2002/06/service/user">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="use:getLoginTicketResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<use:ticket>b49a94fb6d3bfd79f566a32f99a8eaf0f60bdd7a9a8cbfa7f24ca5d63fd2bc0b</use:ticket>
<use:apiVersion>WebEx XML API V10.0.0</use:apiVersion>
<use:webExID>alexxxx</use:webExID>
</serv:bodyContent>
</serv:body>
</serv:message>

Webex site-based XML API supports assign license to users (attendee,host, and site administrators) in external organizations on Control Hub managed sites

Impacted APIs and Schema changes

The XML API: CreateUser, SetUser, and DelUser can assign or revoke meeting site license to an external user (role as: host, attendee, and site administrators). If the users existing in an external organization then the API: CreateUser and DelUser can create or deactivate one user in the meeting site.
If the user doesn't exist in a Control Hub organization and they can't be added to the organization that owns the site, then this call fails.
The XML API: CreateUser and SetUser operation on external organizations users, which limit to change user's firstName, lastName, displayName, webExId, email. If you really have to change this information, you need contact an external organization's administrators to apply the changes.
If the user belongs to another organization which blocks cross-organization licensing, then this call fails.
To license users in an external organization that you must enable organization setting:
- Inviter Administrator Organization - allow-cross-org-assignment
- Invitee Administrator Organization - allow-cross-org-acceptance
For external organizations administrator user meeting license assigning and revoking, we only support use Control Hub administrator account to call the XML API: CreateUser, SetUser, and DelUser on this provision.
The XML API: SetUser can support change user's email in internal organizations user provisioning only if you are a full administration authentication.

There are new exceptions and error codes:

030124 can't change email for an external organization user.
030125 can't change firstName, lastName, or displayName for an external organization user.

Schema changes

No schema change.

Affected APIs:

CreateUser
SetUser
DelUser

API Example:

CreateUser

The API listed here creates a new user in the meeting site (testSite1), and assigns the meeting site license(TC_xxx; SC_xxx) to an external organization user: Jack Smith, because this user existing in Control Hub manged system and under the IBM organization, which is different organization with the meeting site's organization.

POST URL: https://{testSite1}.webex.com/WBXService/XMLService

Body:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<webExID>siteadmin</webExID>
<password>P@ss1234</password>
<siteName>testSite1</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.CreateUser">
<firstName>Jack</firstName>
<lastName>Smith</lastName>
<webExId>Jsmith</webExId>
<email>Jsmith@ibm.com</email>
<password>P@ss1234</password>
<privilege>
<host>true</host>
</privilege>
<active>ACTIVATED</active>
<supportedServices>
<meetingCenter>false</meetingCenter>
<trainingCenter>true</trainingCenter>
<eventCenter>false</eventCenter>
<supportCenter>true</supportCenter>
</supportedServices>
</bodyContent>
</body>
</serv:message>

SetUser

It assigns the meeting site license (MC_xxx, TC_xxx, and EC_xxx) to an external organization user: Jack Smith, and revoke the meeting license (SC_xxx) from Jack Smith.

POST URL: https://{testSite1}.webex.com/WBXService/XMLService

Body:
<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
<securityContext>
<webExID>siteadmin</webExID>
<password>P@ss1234</password>
<siteName>testSite1</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.SetUser">
<webExId>Jsmith</webExId>
<supportedServices>
<meetingCenter>true</meetingCenter>
<trainingCenter>true</trainingCenter>
<eventCenter>true</eventCenter>
<supportCenter>false</supportCenter>
</supportedServices>
</bodyContent>
</body>
</message>

DelUser

It revokes the meeting site and all licenses from an external organization user: Jack Smith; and deactivates the user in the meeting site: testSite1

POST URL: https://{testSite1}.webex.com/WBXService/XMLService

Body:
<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
<securityContext>
<webExID>siteadmin</webExID>
<password>P@ss1234</password>
<siteName>testSite1</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.DelUser">
<webExId>Jsmith</webExId>
</bodyContent>
</body>
</message>

API 42.7.2 Updates

XML API 42.7.2 Updates

Click here to download the XML API 42.7.2 schema.

New XML API: SyncUser

Impacted APIs and Schema changes

New XML API: SyncUser support syncing user info from Control Hub to Webex Meeting system.

If your client hits rate limit, it will response "429 too many requests.", the afterRetry is 25 seconds in API response header.

If the user doesn't exist, it responds to error:" 000031 Control Hub managed user doesn't exist"

If your authentication doesn't have site admin privileges, it responds to error:"000031 Only Site Admin can call this API"

Schema changes

Example API

XML API: SyncUser

API 42.6.0 Updates

XML API 42.6.0 Updates

Click here to download the XML API 42.6.0 schema.

Administrators can't create a new user or modify an existing user when the Webex site is suspended

Impacted APIs and Schema changes

When the Webex site is suspended, then the site administrator can't create new users and modify existing users using XML API: CreateUser and SetUser.

It responds to exception 010107 The site is suspended when one site administrator tries to create a new user or modify one existing user.

The non-administrator user (owner self) are able to modify self information under this suspended site.

Schema changes

No schema change.

Affected APIs:

CreateUser
SetUser

API 42.5.0 Updates

XML API 42.5.0 Updates

Click here to download the XML API 42.5.0 schema.

When the Webex site suspended, it won't allow you to schedule or edit Webinars, Webex Events (classic), Webex Trainings, and Webex Support meetings

Impacted APIs and Schema changes

When the Webex site is suspended, it won't allow you to schedule or edit Webinars, Webex Events (classic), Webex Trainings, and Webex Support meetings, the site only supports free Webex Meetings type.

There are new exception codes and messages: "010107 The site is suspended" when call those APIs ( CreateMeeting, SetMeeting, CreateEvent, SetEvent, CreateTrainingSession, SetTrainingSession, CreateSupportSession) hitting on this limitation.

Schema changes

No schema change.

Affected APIs:

CreateMeeting, SetMeeting
CreateEvent, SetEvent
CreateTrainingSession, SetTrainingSession
CreateSupportSession

API 42.4.0 Updates

There are no schema changes to the XML API 42.4.0 schema.

API 42.3.0 Updates

XML API 42.3.0 Updates

Click here to download the XML API 42.3.0 schema.

XMLAPI has a new ability to send a notification email to the host when the meeting recordings are deleted or reassigned by others

Impacted APIs and Schema change

The XML API: DelRecording sends a notification email to the host when the meeting recordings are deleted or reassigned by others.

Schema changes

No schema change

Affected APIs: DelRecording

DelRecording API sends a notification email to the recording owner when it's operated on by a site administrator.

API request example

XML API: DelRecording example

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
http://www.webex.com/schemas/2002/06/service/service.xsd">
<header>
<securityContext>
<webExID>siteadmin</webExID>
<password>xxxxxx</password>
<siteName>testsite</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.DelRecording">
<recordingID>1234567890</recordingID>
<isServiceRecording>true</isServiceRecording>
<deletePermanently>false</deletePermanently>
</bodyContent>
</body>
</serv:message>

Example of a notification email (moved to trash):

Example of a notification email (permanently deleted):

API 42.2.0 Updates

XML API 42.2.0 Updates

Click here to download the XML API 42.2.0 schema.

GetSite responds to new elements as: `allowChangeFirstName`, `allowChangeLastName`, and `allowChangeDisplayName`

Impacted APIs and Schema changes

The XML API: GetSite returns new elements: allowChangeFirstName, allowChangeLastName, and allowChangeDisplayName. The toggle for this feature is EnableCustomizeProfileFields.

allowChangeFirstName, true or false, means allow the user to change the first name
allowChangeLastName, true or false, means allow the user to change the last name
allowChangeDisplayName, true or false, means allow the user to change the display name

AllowUploadPRAvatar is returned. True or false, means to allow a user to upload an Avatar.

Above changes are only available on non-Control Hub managed sites.

Schema changes

In getSite response, we return new attributes: allowChangeFirstName, allowChangeLastName, allowChangeDisplayName, and AllowUploadPRAvatar under myWebExConfig.

Affected APIs: GetSite

API request and response example

XML API: GetSite example

GetSiteResponse

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="ns1:getSiteResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns1:siteInstance>
...
<ns1:myWebExConfig>
...
<ns1:allowChangeFirstName>false</ns1:allowChangeFirstName>
<ns1:allowChangeLastName>false</ns1:allowChangeLastName>
<ns1:allowChangeDisplayName>true</ns1:allowChangeDisplayName>
<ns1:AllowUploadPRAvatar>true</ns1:AllowUploadPRAvatar>
...
</ns1:myWebExConfig>
...
</ns1:siteInstance>
</serv:bodyContent>
</serv:body>
</serv:message>

API 42.1.0 Updates

XML API 42.1.0 Updates

Click here to download the XML API 42.1.0 schema.

Business logic changed on both XML API: `LstSummarySession` and `GetSessionInfo` on response element: `enableEvent` and `enableWebniar`

Impacted APIs and Schema changes

The XML API: LstSummarySession and GetSessionInfo on response element: enableEvent and enableWebniar, have business logic changed as following:

When enableEvent is true, the meeting is a Webex webinar, false is not a Webex webinar.
If enableEvent is true and then the enableWebniar can be true or false, true means the webinar's attendee only with view-only privileges, false means the webinar's attendee do not limit on view-only privileges.
If enableEvent is false, no meaningful on enableWebniarresponse.

Schema changes

No schema change.

Affected APIs:

LstSummarySession
GetSessionInfo

Add max register limitation per one API call on XML API: `CreateMeetingAttendee`, `RegisterMeetingAttendee`

Impacted APIs

We added 50 maximum registration limitation per one API call on both APIs: CreateMeetingAttendee and RegisterMeetingAttendee.

If client's one time API call registering number of attendees is more than 50, then the APIs response error code and message is:

"040015 Register attendee number over limit in one API call"

Schema changes on API

No schema change.

API request and response example

CreateMeetingAttendee and RegisterMeetingAttendee API request and response Request of CreateMeetingAttendee

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
http://www.webex.com/schemas/2002/06/service/service.xsd">
<header>
<securityContext>
<webExID>host1</webExID>
<password>xxxxxx</password>
<siteName>testsite</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
<person>
<name>test001</name>
<email>test001@test.com</email>
</person>
<sessionKey>987654321</sessionKey>
<attendees>
<person>
<name>test002</name>
<email>test002@test.com</email>
</person>
<sessionKey>987654321</sessionKey>
</attendees>
...
..
<attendees>
<person>
<name>test051</name>
<email>test051@test.com</email>
</person>
<sessionKey>987654321</sessionKey>
</attendees>
</bodyContent>
</body>
</serv:message>

Response of CreateMeetingAttendee

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
<serv:header>
<serv:response>
<serv:result>FAILURE</serv:result>
<serv:reason>Register attendee number over limit in one API call: 50</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>040015</serv:exceptionID>
<serv:value>50</serv:value>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>

API 42.11.1 Updates

XML API 42.11.1 Updates

XMLAPI will LstRecording return as an extra field <recordingUUID>

API 42.11.0 Updates

API 42.11.0 Updates

API 42.10.0 Updates

XML API 42.10.0 Updates

GetSessionInfo API returns a new node <registrationShortURL> that is available in the short-link format for Webex Events (classic) and Webex Trainings

API 42.9.2 Updates

XML API 42.9.2 Updates

XML API will block schedule classic Event after 2023/3/31

API 42.9.0 Updates

API 42.9.0 Updates

API 42.8.1 Updates

XML API 42.8.1 Updates

New XML API: SyncUser

API 42.8.0 Updates

XML API 42.8.0 Updates

GetLoginTicket returns an extra node <webExID>

Webex site-based XML API supports assign license to users (attendee,host, and site administrators) in external organizations on Control Hub managed sites

API 42.7.2 Updates

XML API 42.7.2 Updates

New XML API: SyncUser

API 42.6.0 Updates

XML API 42.6.0 Updates

Administrators can't create a new user or modify an existing user when the Webex site is suspended

API 42.5.0 Updates

XML API 42.5.0 Updates

When the Webex site suspended, it won't allow you to schedule or edit Webinars, Webex Events (classic), Webex Trainings, and Webex Support meetings

API 42.4.0 Updates

API 42.4.0 Updates

API 42.3.0 Updates

XML API 42.3.0 Updates

XMLAPI has a new ability to send a notification email to the host when the meeting recordings are deleted or reassigned by others

API 42.2.0 Updates

XML API 42.2.0 Updates

GetSite responds to new elements as: allowChangeFirstName, allowChangeLastName, and allowChangeDisplayName

API 42.1.0 Updates

XML API 42.1.0 Updates

Business logic changed on both XML API: LstSummarySession and GetSessionInfo on response element: enableEvent and enableWebniar

Add max register limitation per one API call on XML API: CreateMeetingAttendee, RegisterMeetingAttendee

XMLAPI will `LstRecording` return as an extra field <`recordingUUID`>

`GetLoginTicket` returns an extra node <webExID>

GetSite responds to new elements as: `allowChangeFirstName`, `allowChangeLastName`, and `allowChangeDisplayName`

Business logic changed on both XML API: `LstSummarySession` and `GetSessionInfo` on response element: `enableEvent` and `enableWebniar`

Add max register limitation per one API call on XML API: `CreateMeetingAttendee`, `RegisterMeetingAttendee`