Integrations are how you request permissions to invoke the Customer Experience (CX) APIs on behalf of another CX user. To do this securely, we support the OAuth 2.0 standard which allows third-party integrations to get a temporary access token for authenticating API calls instead of asking users for their password.

If you're sure that your integrations require authenticating on behalf of another CX user, read on we'll get you there in a couple of easy steps.

anchorRegistering Your Integration

Registering an integration is super easy. If you're logged in, select My Webex Apps from the menu under your avatar at the top of this page. You'll need to provide some basic information such as the name and description of your integration. This information should be user-facing since that's what they'll see in the permission dialog. You'll also provide redirect URI(s) and scopes during registration. For more information on scopes, please see the section below.

After successful registration, you'll be taken to a different screen that displays your integration's newly created Client ID and Client Secret. The Client Secret will only be shown once so please copy it and keep it safe!

anchorScopes

Scopes define the level of access that your integration requires. The following is a complete list of scopes:

As a general best practice, your integration should request only the scope, or scopes that it needs. For example, if you are creating an application that merely provides data as information to the end user, we recommend using only the read scopes and not the write scopes.

You can always add more scopes from our portfolio by editing your integration in the Webex Developer Portal. To see the list of available scopes (with descriptions) in the Webex Portal, check out this page.

anchorAuthentication

Once you've successfully registered your integration, head on over to the Authentication guide for a step-by-step description of how to configure the OAuth 2.0 authorization flow in your application.