XML AND REST API ACCESS TOKEN

[Patience Umoru]

Hey guys,  

Can i use the access token from the REST API in the XML Api aswell?  

or how do i retrieve the XML access token from the XML API?

Thanks, Jonas

[Patience Umoru]

 First thing to note is that the XML APIs use integrations created through this link : https://developer.cisco.com/site/webex-integration but the REST API use integrations created through https://developer.webex.com/my-apps/new/integration The basics of the two types of integrations are the same, in regards to how you would go through OAuth to generate an access token, but the scopes that can be applied to them are completely different.

Cisco DevNet Meetings Integration/OAuth 2.0:

https://developer.cisco.com/docs/webex-meetings/#!integration

• Resulting OAuth Access Token only supported by the XML API's (cannot be used with REST API).  The Access Token is included in the XML request directly using the <webExAccessToken> element in place of the <password> value.
• To create a new Integration, you must login to developer portal as a Full Administrator user with the "Login with Webex Meetings" option (this is only need to create the Integration, it can be authorized by regular host users).

Webex Integration/OAuth 2.0:

https://developer.webex.com/docs/integrations

• Account must be manged in Control Hub or Linked to a Control Hub managed user profile.
• requires spark:all scope
• The Access Token must be exchanged for a session ticket using the XML API AuthenticateUser request.(Once you have obtained the OAuth Access Token using REST API, you can use the XML API to obtain the session Ticket)The session ticket is used for subsequent API requests.

[Ksler]

And why do two different sites need to exist? aren't both 

Webex Integration/OAuth 2.0:
and

Cisco DevNet Meetings Integration/OAuth 2.0:

getting used for the same purpose.

When should i use one or the other?

[Raffaele Lagana]

The integration concepts for both are similar but they were built for different reasons and with different goals. The XML APIs were originally built to be used with older Site Administrator managed sites, they later were made forward compatible with Control Hub managed sites (through linked sites), but only for Meetings APIs. REST APIs were developed directly for Control Hub managed sites. 

As Patience mentioned, they also differ in terms of the scopes that can be assigned. The REST API's OAuth integration does not contain all scopes that XML APIs require, and vice versa the XML API's OAuth Integration does not contain all scopes that REST APIs require. So they needed to be kept separately.

If you are planning to use XML APIs, you use https://developer.cisco.com/docs/webex-meetings/#!integration . When planning to use REST APIs, you use https://developer.webex.com/docs/integrations . 

[Ksler]

Is there a solution for all sites? Not only Control Hub managed or not?
Because private users won't have a control hub managed site, or am i wrong? 
As well as company users won't use their private accounts.

[Raffaele Lagana]

There is no integration solution for both, they are completely separate. REST APIs will eventually replace XML APIs, they weren't built at the same time and so do not share the same OAuth.

I'm not sure what you mean by 'private users', do you mean non-webex account users or guest users created through a guest issuer app? Those wouldn't have any ability to authorize any webex integration, only webex users can do that.