Webex Meetings

Webex Meetings URL API Tips and Tricks

This section describes about the tips and tricks for Webex Meeting URL API.

URL API requires HTTPS for all commands in WBS 26. In the Webex Meetings Services WBS 26 and later releases, all Webex Meetings URL API requests are required to use the encrypted HTTP Secure Sockets Layer. Webex Meetings recommend that the URL API integrations should 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 Meetings. 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 Meetings Customer Service Manager for your site information or specific dates on when your sites or your customer's Webex Meetings sites will be upgraded to WBS 26 or later.

When using the Webex Meetings URL API, you may experience the following unexpected issues:

Meetings not showing up under My Meetings?

Though the meetings will be listed for the host to see in their My Meetings area, meetings created through the Webex Meetings 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.

Using the java client by default

Meetings scheduled through the Webex Meetings API and joined through the Webex Meetings 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.

Attendee list

Meetings started through the Webex Meetings API are not displaying the attendee list to those joined 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.

Profile Access

The Webex Meetings API allows modifying the profile information such as email 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 knows 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 Emails

Notification emails are not sent when a meeting is scheduled through the Webex Meetings 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.

Common Entry Point (CEP) Tips

When using the Webex Meetings URL API, you may experience the following most common error messages:

  • Unique Identifiers

    Webex Meetings uses a combination of the host login (WID) and the email address (EM) as unique identifiers to ensure no duplication of host accounts. This reduces the potential for issues with billing and usage tracking. For more information, see WebexIDConflict.

  • WebexIDConflict

    This error occurs when the Webex Meetings API is used to create a host account using the information that is already in the Webex Meetings database. This error occurs in the following scenarios:

  • The WID is already in use but the email address associated with it is not in use.

  • The email address is already in use but the WID associated with it is not in use.

  • Both the email address and the WID are already in use.

  • Access Denied

    Webex Meetings uses a session cookie to keep track of the authenticated host. This session cookie is attached to the browser from where it originates from.

Typically the host will receive this error for one of the following 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.

  • BadWebexID or Password

    This error occurs when the WID and PW combination that are sent, do not match with what is in the Webex Meetings database.

Next