Chat with Us!

WebEx Web Conferencing XML API FAQ


 

Question Index

 

How do I get my WebEx Web Conferencing Site ID (SID) and/or Partner ID (PID)?
Contact your WebEx Web Conferencing Account Manager (CSM).

How do I send an XML message to your server?
The XML API uses standard HTTP(S) POST requests for placing API calls. We strongly recommend you use HTTPS since the includes your WebEx Web Conferencing username and password in each call.

What is the URL I post my XML API to?
The normal URL to post your XML API request is https://[SITENAME].webex.com/WBXService/XMLService. SITENAME is usually the name of the customer organization.

Is there a way for me to test the next XML API release before it is deployed on my site?
Yes, we will always notify you at least two weeks in advance before releasing a new version of the XML API. During this time we can provide you with a "sandbox" site where you can test your integration with the upcoming release. Usually two weeks before its production rollout, we will make the next release available directly on your site via a "preview" URL. The format for this URL is https://SITENAME.webex.com/WBXService/preview/XMLService where SITENAME is your WebEx Sitename.

How do I get the latest release of the API documentation?
The latest XML API documentation is available at in the Documentation section on this site.

Can I make SOAP calls to the XML API?
Currently, the WebEx Web Conferencing XML API does not utilize SOAP envelopes in our request or response format nor publish WSDL files. However, the XML API service responds to XML requests posted via HTTP. Customers have successfully used XSL Transformations or other methods to transform SOAP calls into the WebEx Web Conferencing XML API format.

What do I use for <meetingType> in CreateMeeting?
<meetingType> is an integer value used to specify the Meeting Type for the meeting you are scheduling. This value can change from site to site and user to user.



The easiest way to set the Meeting Type is to leave out <meetingType> in CreateMeeting. In this case the system will automatically determine a proper meeting type based on the following criteria:

  1. Among all the meeting types allowed for a host, choose an Meeting Center (MC) PRO based meeting type with the highest meeting type ID.
  2. If unavailable, choose an MC STD based meeting type with the highest meeting type ID.
  3. If unavailable, choose an MC FRE based meeting type with the highest meeting type ID.
  4. If none of the meeting types are available, the system throws an exception.

To manually specify a <meetingType> the integration should first call GetUser to retrieve the available meeting types for the user scheduling the meeting.