ZTA LabFree University

T3 · T3-R08 · Talkdesk

Talkdesk OAuth, account or user

Choose the grant from the audience. A customer automating their own instance is the Client Credentials case the page describes. An AppConnect partner signing a user in is the Authorization Code case. The page also names Signed JWT in the documentation index beside those grants. This room quotes the two grants the authentication page's opening table defines.

ExportSVGFlowSheet

Learn it in 5 minutes

  • The authentication page says Talkdesk supports OAuth 2.0.
  • Client Credentials are for account-level access, on behalf of an entire Talkdesk account.
  • Authorization Code is for user-level access, on behalf of a single user.
  • The page's front matter shows updatedAt 2026-09-10.
  • Client secrets do not belong in this lab.

Visual

Talkdesk OAuth, account or user OAuth. Teaching sketch. Confirm a live system. Client Credentials Authorization Code Account User Names come from pages opened in 2026-10. A missing name stays confirm.

Count the boxes: 4. Each label is a name from a page or a study label marked on the drawing.

Flow

Talkdesk OAuth, account or user Caller SIP Called session setup session setup RTP, not required to hairpin Teaching sketch from RFC 3261 and RFC 3550. Not a packet capture.

What is going on

Choose the grant from the audience. A customer automating their own instance is the Client Credentials case the page describes. An AppConnect partner signing a user in is the Authorization Code case. The page also names Signed JWT in the documentation index beside those grants. This room quotes the two grants the authentication page's opening table defines.

The same page links a support request form. This session opened the authentication markdown, not that form. Do not debug a 403 on the support host by guessing the form fields.

Scopes are a separate docs page linked from authentication. This session did not open the scopes page, so scope names stay confirm.

Worked example

An integration uploads schedules for the whole account. Write Client Credentials and the reason: account-level access. An app that acts as one supervisor writes Authorization Code. Write the doc date you saw, 2026-09-10, as the page's updatedAt, not as a product release.

Quiz

1. Client Credentials are described as account-level access.

2. updatedAt 2026-09-10 is a Talkdesk product release date.

Ecosystem

Sister pieces sit on the ecosystem page: the glossary, the mind map, the integration map, and the bridges.

  • Client Credentials — The OAuth grant the Talkdesk page describes for account-level API access.
  • Authorization Code — The OAuth grant the page describes for access on behalf of one Talkdesk user.

Config. Write the grant and the audience. Store the secret outside the repo.

Troubleshooting. A user-scoped action failing with an account token matches the split on the page. Change the grant before you change the dial plan.

Bridge. Zoom's API also uses OAuth and a one-hour token. Talkdesk's page does not state that lifetime. Do not copy the Zoom hour onto Talkdesk.

Mind map, sister technologies, and future hooks live on the ecosystem page.

Sources and go deeper

Opened 2026-10. A row marked confirm has no link, because that page was not verified.

sources.json Markdown