The objects available within our connector are accessible from the "cdata.talkdesk" module. To use the module's objects directly:

1. Import the module as follows:
   

   import cdata.talkdesk as mod

2. To establish a connection string, call the connect() method from the connector object using an appropriate connection string, such as:
   

   mod.connect("AccountName=myAccount;Region=US;OAuthClientId=myClientId;OAuthClientSecret=myClientSecret;")

Connecting to Talkdesk

To connect to Talkdesk, set the following properties:

• AccountName: The name of your Talkdesk account.
• Region: The region where your Talkdesk instance is deployed. Supported values are US (default), EU, CA, AU, UK, and FedRamp.
• OAuthClientId: The Client Id assigned when you registered your custom OAuth application.
• OAuthClientSecret: The Client Secret assigned to your custom OAuth application. See Creating a Custom OAuth Application for instructions on registering the application.

When you open the connection, the connector automatically requests an access token from Talkdesk and caches it. The token is refreshed automatically when it expires.

Authenticating to Talkdesk

Talkdesk supports the OAuth 2.0 Client Credentials grant flow. No browser-based authorization or callback URL is required.

OAuth Client Credentials

Authenticating with client credentials requires the creation of a custom OAuth application, as described in Creating a Custom OAuth Application.

To enable authentication, set these properties:

• AccountName: The name of your Talkdesk account.
• Region: The region where your Talkdesk instance is deployed. Supported values are US (default), EU, CA, AU, UK, and FedRamp.
• OAuthClientId: The Client Id assigned when you registered your OAuth application.
• OAuthClientSecret: The Client Secret assigned when you registered your OAuth application.

Use InitiateOAuth to control how the connector manages tokens:

• GETANDREFRESH (default): The connector requests a new access token on first connection and refreshes it automatically when it expires.
• REFRESH: The connector uses the token cached in OAuthSettingsLocation and refreshes it when needed. Use this setting after a prior GETANDREFRESH connection has populated the settings file.
• OFF: The connector does not request or refresh tokens. Provide a valid token via OAuthAccessToken and manage refresh yourself.

The OAuthSettingsLocation property specifies where the connector stores the cached access token. The default is OAuthSettings.txt in the current working directory. When using multiple connections with the same driver, set a distinct path for each connection to prevent one connection from overwriting another's cached token.