Zendesk · Authentication Profile

Zendesk Authentication

Authentication

Zendesk secures its APIs with http and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

ChatCRMHelp CenterSellSupportT1TalkTicketingTickets
Methods: http, oauth2 Schemes: 3 OAuth flows: authorizationCode API key in:

Security Schemes

basicAuth http
scheme: basic
bearerAuth http
scheme: bearer
OAuth2 oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-06-20'
method: searched
source: openapi/zendesk-support-openapi.yml
docs: https://developer.zendesk.com/documentation/api-basics/authentication/
notes: >-
  Zendesk supports three request-authentication styles: (1) Basic auth with an
  API token, sent as "{email_address}/token" with the API token as the password;
  (2) Basic auth with an agent password (discouraged, being phased out); and
  (3) OAuth 2.0 access tokens presented as an HTTP bearer credential. OAuth uses
  the authorization-code flow with read / write / impersonate and
  resource-qualified scopes (see scopes/zendesk-scopes.yml). As of 2026-01-16
  Zendesk enforces default token TTL and requires the refresh-token flow for
  global OAuth clients.
summary:
  types:
  - http
  - oauth2
  http_schemes:
  - basic
  - bearer
  oauth2_flows:
  - authorizationCode
schemes:
- name: basicAuth
  type: http
  scheme: basic
  description: 'Use your Zendesk email address followed by /token and your API token as the
    password. For example: user@example.com/token:api_token'
  sources:
  - openapi/zendesk-support-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  description: OAuth 2.0 access token presented as a bearer credential.
  sources:
  - openapi/zendesk-support-openapi.yml
- name: OAuth2
  type: oauth2
  flow: authorizationCode
  authorizationUrl: https://{subdomain}.zendesk.com/oauth/authorizations/new
  tokenUrl: https://{subdomain}.zendesk.com/oauth/tokens
  scopes: scopes/zendesk-scopes.yml
  sources:
  - docs