cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
837
Views
0
Helpful
1
Replies

Cisco WebEx XML API

sandiyaanandraj
Level 1
Level 1

Hi, Im working on integrating Cisco WebEx Teleconferencing feature with my web application. For that cisco has provided with XML APIs. And the API involves sitename. Im not sure about the structure of the API's url. As far as I understood, I have structured the API as below. But Im not able to get any reponse for the API if I post the API with the parameters like siteId, WebExId and password.

 

Structure of the API url:

https://mysiteName/WBXService/XMLService

 

I doubt if I have to pass API Key and access token parameters to the API. Can anyone please guide me on this. 

1 Accepted Solution

Accepted Solutions

athapaCisco
Level 1
Level 1

The URL is correct , you might be not using the correct syntax as the webexID thing uses mixed bag of upper/lower cases, here is an example of GetUser

 

<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <header>
    <securityContext>
      <webExID>yourid@domain.com</webExID>
      <password>yourpassword</password>
      <siteName>yourSitename</siteName>
    </securityContext>
  </header>
  <body>
    <bodyContent
      xsi:type="java:com.webex.service.binding.user.GetUser">
    		<webExId>Useryouwant@domain.com</webExId>
          </bodyContent>
  </body>
</serv:message>

View solution in original post

1 Reply 1

athapaCisco
Level 1
Level 1

The URL is correct , you might be not using the correct syntax as the webexID thing uses mixed bag of upper/lower cases, here is an example of GetUser

 

<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <header>
    <securityContext>
      <webExID>yourid@domain.com</webExID>
      <password>yourpassword</password>
      <siteName>yourSitename</siteName>
    </securityContext>
  </header>
  <body>
    <bodyContent
      xsi:type="java:com.webex.service.binding.user.GetUser">
    		<webExId>Useryouwant@domain.com</webExId>
          </bodyContent>
  </body>
</serv:message>