Create Webex security tokens for Cisco Webex Calling

The registered integration is used to request permissions to invoke the Cisco Webex Calling API. To do this securely, Webex uses the OAuth 2.0 standard security tokens. You create the tokens on the Webex portal. This integration requires two tokens: an access token and a refresh token.

The access token usually expires after 6 to 12 hours and the refresh token usually expires in 60 days.

Follow this procedure the first time you create the Webex security tokens.

Before you begin

  • Have the Client ID and Client Secret that were issued while registering Verint as a Webex App on the Cisco Webex Developer Portal.

  • Have a server running the Verint Recorder application.

Procedure 

  1. Sign in to developer.webex.com using administrator credentials for your Webex account.

  2. Using cURL or Postman, send a POST request to https://webexapis.com/v1/access_token using the following parameters:

    Parameter

    Value

    grant_type

    Set to authorization_code.

    client_id

    The Client ID issued to the Verint integration.

    client_secret

    The Client Secret issued to the Verint integration.

    code

    The authorization code for the Verint integration.

    redirect_uri

    A valid URL. You can use https://oauth.pstmn.io/v1/callback.

    Example Request

    The example shows the API request using cURL. You can copy the code below and replace the client ID, client secret, and code with the ones for your Webex integration.

    Copy
    curl --location --request POST "https://webexapis.com/v1/access_token" --header
    "Content-Type: application/x-www-form-urlencoded" --data-urlencode "grant_
    type=authorization_code" --data-urlencode "client_
    id=C6db11fc58941f550a69165XXXXXXXXXXXXXXXX" --data-urlencode
    "client_secret=0f322184b7384f0d269f1XXXXXXXXXXXXX" --
    data-urlencode "redirect_uri=https://oauth.pstmn.io/v1/callback" --data-urlencode
    "code=ZTQyYWVjNGQtMmFjOS00ZWUwXXXXXXXXXXXXXXXX"

    Example Response

    The response contains the access token and the refresh token. The expires_in times are measured in seconds.

    Copy
    {
        "access_token": "MTI4OTRkYmQtNjQ4Yi00OTBlLTXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "expires_in": 1209599,
        "refresh_token": "NGI4ZGJkNTEtNjlmMS00ZjI2LTgXXXXXXXXXXXXXXXXXXXXXX",
        "refresh_token_expires_in": 7775999,
        "token_type": "Bearer",
        "scope": "spark:kms spark:people_read identity:tokens_write identity:tokens_read spark-compliance:recordings_read"
    }
  3. Copy the refresh token to use when you create the data source.

What to do next 

Set up the Recorders for Cisco Webex Calling

Get Webex authorization code for Cisco Webex Calling

Integration configuration for Cisco Webex Calling

Related information