Configuring Vonage Contact Center API authentication tokens

Your Salesforce org stores authentication tokens for Vonage Contact Center APIs in a secure area—Secrets Management.

How do I add or update an authentication token?

Before you configure tokens, you must have set your account key—or keys, if you have configured different custom settings for your org, profiles, and users—in custom settings. For information about setting your account key, see Configuring custom settings for optional Vonage Contact Center features in Salesforce.

To add or update an authentication token, perform the following steps:

1. Go to the Secrets Management tab in your ContactWorld for Salesforce or Vonage Contact Center (depending on whether you are using Salesforce Classic or Salesforce Lightning Experience) app within Salesforce. Secrets Management appears.

   Secrets Management contains a list of secrets. Each secret consists of the following values:

   Label	Description
   Client ID	Represents a ContactWorld Account Key in one of your custom settings records.
   Locations	Locations indicates which location—or locations, if you have configured different custom settings for your org, profiles, and users—uses the secret.
   API token set?	Indicates whether this secret already has an associated API token.

   If the list is empty, you must go back and add a value in ContactWorld Account Key fields in each of your custom settings records. Providing values in these fields will create a corresponding secret for each of your account keys.
   • If you have previously configured account keys and tokens in custom settings—in older versions of the Vonage Contact Center package—Vonage will have copied the token to the secret and deleted it from custom settings.
2. To add or update an API token for a secret, click Update Token alongside the secret. Update Token appears.

3. Provide the token that corresponds to the Client ID. For information about finding your API token, see Getting your account key and API authentication token. Click Save. The secret is saved.

   Secrets Management only indicates whether the secret has a token or not. For security reasons you cannot see the value of tokens after they have been set.