cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2639
Views
0
Helpful
3
Replies

Webex API

julius_bun
Level 1
Level 1

Hi,

My client is interested in embedding the Webex Meeting on the website so end-user could join to Webex for remote troubleshooting.  Is it possible with Webex API? Could the embedded do normal screen sharing and mouse control for normal troubleshooting? Also my client has Webex subscription so is there a cost involved to use this API? Any other licensing cost or forum cost?

Regards,

Julius.

1 Accepted Solution

Accepted Solutions

Julius,

let me try to simplify the above descriptions, its not very clear and full of buzzwords.

URL API: simple api used to issue WebEx commands via web based form post.  All the commands are sent by, and returned too, the browser of the client.. We suggest all new integrations lean towards the XML API as its far more robust and easier to work with programatically.

XML API: robust API for managing most of the functions you can see on your WebEx site, can be used for custom web portal or desktop/mobile applications.


TSP API: for telephone service providers, to integrate 3rd party voice conferencing with WebEx.

the URL API and XML API basically manage your WebEx site, you can wrap your own interface around it and do many of the same tasks avilable programatically. However once the meeting has started its all left up to the native WebEx client for whatever platform the users are on. The meeting client will be launched externally, and the only thing these WebEX APIs can do to a meeting in progress is terminate it.

What you do with these APIs are up to you, most use them to create their own portal with desired workflows, others use it simply to allow quick and easy access for launching meetings, you have endless possibilities.

View solution in original post

3 Replies 3

ryanhunt
Level 5
Level 5

The API's only allow commands pre-meeting and post-meeting, they do nothing for meetings in progress.. the WebEx client cannot be embedded into a website, with the API's all you could do is generate a link for them to click that would launch the WebEx Client Application.

Hi Ryan,

But i read the description in Webex API:

The WebEx Meeting Services API Platform lets users incorporate Cisco WebEx meetings into their own applications. The platform offers three APIs: URL API: The URL API is a convenient, lightweight, HTTP(S)-based mechanism that provides browser-based, external hooks into WebEx meeting services. The URL API is typically used in enterprise portal integrations to support basic interactions such as Single Sign-On (SSO), scheduling meetings, starting and joining simple meetings, and inviting attendees and presenters. XML API: The XML API is a comprehensive set of services that supports most aspects of WebEx meeting services, including detailed user management, comprehensive scheduling features, attendee management and reporting, and more. The WebEx XML API employs a services oriented architecture (SOA) to provide comprehensive services to external applications wishing to interact with one or more WebEx services. Teleconference Service Provider (TSP) API: The TSP API provides full-featured XML-based integration with audio conferencing networks. The integration architecture supports redundancy, fail-over, and load balancing, and provides robust features that tightly integrate audio conferencing capabilities with telephony management and provisioning in the WebEx environment.


What kind of application can the API be embedded to ?

So basically it just generate a webex link for the API?


Regards,

Julius.

Julius,

let me try to simplify the above descriptions, its not very clear and full of buzzwords.

URL API: simple api used to issue WebEx commands via web based form post.  All the commands are sent by, and returned too, the browser of the client.. We suggest all new integrations lean towards the XML API as its far more robust and easier to work with programatically.

XML API: robust API for managing most of the functions you can see on your WebEx site, can be used for custom web portal or desktop/mobile applications.


TSP API: for telephone service providers, to integrate 3rd party voice conferencing with WebEx.

the URL API and XML API basically manage your WebEx site, you can wrap your own interface around it and do many of the same tasks avilable programatically. However once the meeting has started its all left up to the native WebEx client for whatever platform the users are on. The meeting client will be launched externally, and the only thing these WebEX APIs can do to a meeting in progress is terminate it.

What you do with these APIs are up to you, most use them to create their own portal with desired workflows, others use it simply to allow quick and easy access for launching meetings, you have endless possibilities.