Refresh Webex security tokens for Cisco Webex Meetings

Settings in the data source create a security token required to use the Cisco Webex API. The Verint adapter refreshes this token on startup. If the adapter is not run for over 60 days, and the refresh token expires, you must generate a new one.

Before you begin

• Get an application to make API requests. You can use cURL or Postman.

• Authorize Verint in Cisco Webex Meetings

Procedure 

1. Send a POST request to https://webexapis.com/v1/access_token using the following parameters:

   Parameter	Value
   grant_type	Set to refresh_token.
   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. If you don't have a code or it has expired, get the Webex Authorization code now.
   redirect_uri	A valid URL. You can use https://oauth.pstmn.io/v1/callback.

   Example:  

   The example shows the API request using cURL. You can copy the sample code below and replace the client ID, client secret, and code with the ones for your Webex integration, as the ones shown here are samples only.

   Copy

   curl --location --request POST 'https://webexapis.com/v1/access_token' \
   --header 'Content-Type: application/x-www-form-urlencoded' \
   --data-urlencode 'grant_type=refresh_token' \
   --data-urlencode 'client_id=C6db11fc58941f550a69165c342f653f71b601523ad9f3d9432ac596c9a6e6077' \
   --data-urlencode 'client_secret=0f322184b7384f0d269f1a8ca38646f57dbe46782f9fd77ed3c99cc05e7a2997' \
   --data-urlencode 'redirect_uri=https://oauth.pstmn.io/v1/callback' \
   --data-urlencode 'code=ZTk4Y2EyMTYtZjljMS00OWIxLTgwZWEtNzVkZmIwODAxZThmZjcxYjlhNDItYjdh_PF84_c6f92e5d-cbc1-4fe3-8789-caf3b283bf4b'

   Response

   The response contains new access and refresh tokens.

2. Copy the refresh token, and then update the data source.

Related topics 

Create the Cisco Webex Meeting Audio Capture Adapter