URL API will require HTTPS for all commands in WBS 26
In the WebEx Services WBS 26 and later releases, all WebEx URL API requests are required to use the encrypted HTTP Secure Sockets Layer.
WebEx has long recommended that URL API integrations use encrypted "https://" for security reasons and WBS 26 will enforce this. If URL API commands are sent using standard HTTP, these commands can be "sniffed" as they travel over the Internet from customer servers to WebEx. All URL API calls should be preceded by "https://" instead of "http://".
For example, the unencrypted command:
http://acme.webex.com/acme/m.php?AT=JM&MK=12345678
should be changed to:
https://acme.webex.com/acme/m.php?AT=JM&MK=12345678
Please contact your WebEx Customer Service Manager for your site information or specific dates on when your sites or your customer's WebEx sites will be upgraded to WBS 26 or later.
Unexpected things that happen when using the WebEx URL API
Though they will be listed for the host to see in their My Meetings area, meetings created via the WebEx API are not listed in the Meeting Calendar by default. However, the LF=1 parameter can be added in the AT=SM or AT=IM command to set the list flag to "on" to list the meeting in the Meeting Calendar as well as the Today's Meetings page.
Meetings scheduled via the WebEx API and joined via the WebEx Interface are joined using the Java client by default. This can be controlled programmatically by supplying the appropriate MF parameter with the AT=SM or AT=IM command. Contact API Support Services to determine the correct MF value for your site.
Meetings started via the WebEx API are not displaying the attendee list to those joining the meeting by default. This can be controlled programmatically by supplying the appropriate MF parameter with the AT=SM or AT=IM command. Contact API Support Services to determine the correct MF value for your site.
The WebEx API does allow for modification of profile information such as e-mail address, phone number, department, company name, etc., using the AT=MO. The caveat for this command is that the login command must be issued first so that the system know the changes are authorized. If the only change desired is to change the password, this can be quickly done by including the new password information in the NPW parameter with the AT=LI command along with the existing password in the PW parameter.
Notification e-mails area not sent when a meeting is scheduled via the WebEx URL API (AT=SM). Invitations are sent when attendees are added to a meeting (AT=AA).
An invitation can also be sent from within a meeting room once the meeting has started.
When testing, feel free to use http://developers.webex.com/api/httpvars.php as your BU address. It will just print out all parameters it was called with. This makes it easy to quickly see whether the command succeeded or failed and the resulting error, if any.
Common Entry Point (CEP) Tips
e.php?AT=MO
e.php?AT=TM
Most Common Error Messages
WebEx uses a combination of the host login (WID) and the e-mail address (EM) as unique identifiers to ensure no duplication of host accounts. The reduces the potential for issues with billing and usage tracking. See more in WebExIDConflict.
This error occurs when the WebEx API is used to create a host account using information that is already in the WebEx database. This error occurs when:
The WID is already in use but the e-mail address associated with it is not. The e-mail address is already in use but the WID associated with it is not. Both the e-mail address and the WID are already in use
WebEx uses a session cookie to keep track of the authenticated host. This session cookie is attached to the browser it originates from. Typically the host will receive this error for one of two reasons:
The host has been inactive for over 20 minutes
The host logged in with one instance of the browser and is trying to access features using a different instance.
This error means that the WID and PW combination sent do not match what is in the WebEx database.
