Credentials tab

The information required to access a runtime service is found in the Credentials tab for each deployed application configuration.

To access Credentials:

  1. In the Mix dashboard, click the Manage tab.
  2. Click the Applications tab.
  3. Select the application you want to access.
  4. On the left panel, select the context tag you want to see credentials for.
  5. Click Credentials.

The Credentials & IDs for the context tag appear.


The credentials for each geography are shown under the environment where the application configuration is deployed. Credential blocks are listed to the right of the geography. They include a JSON file to authorize your client application, as well as access parameters for each type of service used by your application configuration.

The credentials listed are specific to an environment geography. For example, credentials for Dev-Sandbox US are different from credentials for Prod US.

The table below summarizes the four types of Credential blocks:

Credential blocks
Credential block Description
config.json Contains the configuration needed to authorize the client application in the selected environment, in JSON format.
asr_params Contains the URN parameter to access your ASR DLMs application.
nlu_params Contains the URN parameter to access your NLU model application.
dlg_params Contains the URN parameter to access your Dialog application.

Select each credential block to see the code needed in your client application. You can copy the block by selecting Copy Credential Block.

Here is a sample config.json file:

"client_id": "appID:NMDPTRIAL_firstname_lastname_nuance_com_20201005T202248318244:geo:us:clientName:default",
"client_secret": "CLIENT_SECRET", /* to be filled by user */
    "oauth_server_url": "",
    "oauth_scopes": "asr dlg nlu tts log asr.wordset nlu.wordset",
    "asr_endpoint": "",
    "nlu_endpoint": "",
    "tts_endpoint": "",
    "dlg_endpoint": ""

This table describes the current parameters for config.json.

config.json parameters
Parameter Description
client_id Provides the client ID needed to access the environment. There can be multiple client IDs. All client IDs defined for an environment geography will be listed in the config.json file.
client_secret A client secret is needed to access the environment geography. See Generate the client secret for more information.
oauth_server_url Provides the authorization URL. For example,
oauth_scopes Lists the scopes that are available for the client IDs in this environment geography.
asr_endpoint Provides the URL of the ASRaaS.
nlu_endpoint Provides the URL of the NLUaaS.
tts_endpoint Provides the URL of the TTSaaS.
dlg_endpoint Provides the URL of the DLGaaS.