verapli
Sign inJoin free
Menu

Guides · messaging · Popular APIs

Zendesk API (API token, OAuth client, global OAuth client)

Admins create API tokens or OAuth clients in Admin Center. Zendesk is removing API tokens (migrate to OAuth before 30 April 2027). Apps for many Zendesk customers need a global OAuth client approved via the Marketplace portal.

Researched · not yet run liveLast researched 25 October 2026 · Zendesk · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

Tokens and OAuth clients belong to a Zendesk account ({subdomain}.zendesk.com); global OAuth uses a d3v- sponsored developer account.

  • Zendesk account organisationAdministrator role required.
  • Zendesk Marketplace partner portal / d3v- sponsored account developeroptionalOnly for global OAuth clients.

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Create an API token (being retired)optional

    In Admin Center > Apps and integrations > APIs > API tokens, click Add API token, add a description and Save; copy it before closing.

    • verapli co-pilot
    • Human step: You press submit

    verapli captures ZENDESK_API_TOKEN here by plain code: encrypted in your browser, never shown to AI.

    Where: https://{subdomain}.zendesk.com/admin/

  2. Add an OAuth client

    Admin Center > Apps and integrations > APIs > OAuth clients > Add OAuth client. Enter name, identifier, https redirect URLs and client kind (Public needs PKCE). Save, copy the secret (shown once), Save again.

    • verapli co-pilot
    • Human step: You press submit

    verapli captures ZENDESK_OAUTH_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.

    Where: https://{subdomain}.zendesk.com/admin/

  3. Request a global OAuth client (apps for many customers)optional

    Build a local client with a zdg- identifier in your d3v- sponsored account, fill every field, save the secret, then in the Marketplace portal choose Global OAuth > Request new OAuth listing only needed scopes.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Add an OAuth client
    If something goes wrong (1)
    • invalid_scope errors after approval: Zendesk may limit the global client's allowed scopes; request only those. [3]

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can get you bannedThe rules say

Zendesk is removing API tokens; integrations must migrate to OAuth access tokens before April 30, 2027. [1]

Can cost moneyThe rules say

Apps distributed to multiple Zendesk customers must use a global OAuth client; customers' API tokens are not allowed. [3]

What you end up with

Env varSecretFormatWhat it is
ZENDESK_SUBDOMAINnot secretyourcompanyYour Zendesk subdomain
ZENDESK_EMAILnot secretadmin@example.comAdmin email used with an API token
ZENDESK_API_TOKENsecretopaque token stringAPI token (removed from Zendesk by April 30, 2027)
ZENDESK_OAUTH_CLIENT_IDnot secretyour-chosen-identifier (zdg-… for global clients)OAuth client unique identifier
ZENDESK_OAUTH_CLIENT_SECRETsecretopaque secret stringOAuth client secret

For agents

The same entry as JSON: /api/v1/entries/zendesk/api · requirements /api/v1/requirements/zendesk/api · terms /api/v1/terms/zendesk/api.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Zendesk API (API token, OAuth client, global OAuth client), and how long will it take?"
  → tools/call requirements { "provider_id": "zendesk/api" }

Sources

  1. Managing API token access to the Zendesk API Admins only; Admin Center > Apps and integrations > APIs > API tokens > Add API token; full token never displayed again; up to 256 tokens (2048 for accounts already above 256); token access must be enabled; API tokens being removed, migrate to OAuth before April 30, 2027. · accessed 25 October 2026 · official
  2. Using OAuth authentication with your application Admin Center > Apps and integrations > APIs > OAuth clients > Add OAuth client; name, identifier (client_id), https redirect URLs (localhost/127.0.0.1 excepted), client kind Public (PKCE required) or Confidential; secret shown in full once (then first nine characters). · accessed 25 October 2026 · official
  3. Set up a global OAuth client Public/multi-customer apps need global OAuth; build a local client with a zdg- identifier in a d3v- sponsored account, save secret, request via Marketplace portal > Global OAuth > Request new OAuth; Zendesk reviews and may restrict allowed scopes; no timeline stated. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Zendesk is not affiliated with verapli.