Token Generation via OAuth

Publisher

Dialpad

URL

https://developers.dialpad.com/docs/oauth.md

Published

2026-09-23

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Dialpad website terms; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• For use within a single company, a Dialpad administrator can create an API key instead of implementing OAuth. in context
• The authorization code returned in Dialpad's three-legged OAuth flow is valid for one minute. in context
• Dialpad OAuth uses /oauth2/authorize, /oauth2/token and /oauth2/deauthorize on sandbox.dialpad.com for sandbox and dialpad.com for production. in context
• Dialpad recommends PKCE (code_challenge and code_verifier per RFC 7636) for its OAuth authorization flow. in context
• Dialpad issues refresh tokens only when the offline_access scope is granted, and a refresh returns a new access token and a new refresh token. in context

Cite this source record

APA

WarmTransfer. (2026, September 23). Token Generation via OAuth. WarmTransfer. https://warmtransfer.net/knowledge/sources/dialpad-dev-oauth

BibTeX

@misc{warmtransfer-dialpad-dev-oauth,
  title  = {Token Generation via OAuth},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/dialpad-dev-oauth},
  note   = {Dialpad, accessed 2026-09-24}
}