Partner App Authentication

Using the Access Token

The access token is the required string to make requests to the Talkdesk® APIs.

Once it is retrieved, it can be used to make requests to the Talkdesk APIs.

It must be used in the Authorization header of the HTTP calls to sign the request.

GET https://api.talkdeskapp.com/reports/calls/jobs/{id} HTTP/1.1
Authorization: Bearer ACCESS_TOKEN
Content-Type: application/json
curl https://api.talkdeskapp.com/reports/calls/jobs/{id} \
-H 'Authorization: Bearer ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
-X GET

🚧

Token Expiration

For security purposes, access tokens are valid for 10 minutes. If a 401 unauthorized error is received, at any point, the Authentication page shows how to retrieve a new access token.

🚧

Region Agnostic Access to Talkdesk APIs

When using the Events API to get access to OAuth client credentials, you must make sure to use the value of the root link provided in the events (including app.installed) for the customer.
If you use a hard-coded value of a specific API Gateway, instead, the app will only work for customers using that region's infrastructure. In the example above, accessing the Reporting API via https://api.talkdeskapp.com/ would only work for apps running in the US.

Authenticating via AppConnect

Talkdesk AppConnect™ is a marketplace that connects the user with contact center apps, devices and services. Each app operates with a one-click installation and a 30-day free trial.

AppConnect apps leverage the Talkdesk authentication mechanisms to provide a fully integrated experience.

Each Talkdesk customer account and corresponding app installation are provided with a distinct set of API credentials:

  • Client ID.
  • Client secret.
  • JWT key-value.

These credentials are leveraged to initiate:

🚧

To validate Events API from Talkdesk that allow to subscribe to installation, update, trial expiration events, etc., the signing mechanism must be leveraged.


Did this page help you?