Create Webex security tokens for Cisco Webex Meetings

The registered integration is used to request permissions to invoke the Cisco Webex 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 a refresh token.

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

Follow this procedure the first time that you create the Webex security tokens. If you need to refresh expired tokens, see Refresh Webex security tokens for Cisco Webex Meetings.

Before you begin

Get Webex authorization code for Cisco Webex Meetings
Have the Client ID and Client Secret that were issued when you Register Verint as a Webex App for Cisco Webex Meetings.
Have a server running the Verint Recorder application.
Get an app to make the API requests, like cURL or Postman.

Procedure

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. If you don't have a code or it has expired, Get Webex authorization code for Cisco Webex Meetings
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, 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=authorization_code" --data-urlencode "client_id=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=xxxxxxxx" --data-urlencode "client_secret=zzzzzzz" -- data-urlencode "redirect_uri=https://oauth.pstmn.io/v1/callback" --data-urlencode "code=ZTQyYWVjNGQtMmFjOS00ZWUwLWI3MDMtNGQxMDEwZTMwNzM5YjVkOWE0N2EtNDRj_PF84_c6f92e5d-cbc1- 4fe3-8789-caf3b283bf4b"

Example Response

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

Copy

{
    "access_token": "MjY5NzVjODktNzk3OC00YTc3LTkyZWUtMzg0NGM4YjExNWZhM2EyYjM3MWMtM2Zh_P0A1_02559c32-1892-44dd-ba2b-6580c06deabb",
    "expires_in": 1209599,
    "refresh_token": "YjY1NGNmZjctYmMxNC00MGE3LTgyNTktYTExMmEyZTdlODZkMTVkNGE3YzMtMjJh_P0A1_02559c32-1892-44dd-ba2b-6580c06deabb",
    "refresh_token_expires_in": 7775999,
    "token_type": "Bearer",
    "scope": "meeting:admin_participants_read meeting:admin_recordings_read meeting:admin_schedule_read identity:tokens_read identity:tokens_write
 "
}

Copy the refresh token to use when you create the data source.

What to do next

Create the Cisco Webex Meetings data source