Zendesk
HardOAuth clients are per Zendesk subdomain, so a local client only works for one account; to let any Zendesk customer connect you need Zendesk to convert your client into a global OAuth client, which requires a d3v- sponsored partner account, and since August 2025 multi-customer integrations must also be submitted for Marketplace review.
Agent-researched, not yet reviewed by a personResearched 2026-10-20
Working in dev
30–90 min
Signing in with your own account
Any user can connect
2–6 weeks
A server-side agent that reads and writes tickets across many customers' Zendesk accounts, which needs a global OAuth client plus a Marketplace listing; there is no faster path for third parties.
- Waiting on
- Sponsored d3v- account approval (no stated SLA), the global OAuth client request (no stated SLA), and Marketplace review (1–3 weeks for new apps).
- Cost
- Free: trial and sponsored developer accounts cost nothing. Customers' API rate limits depend on their Zendesk plan.
What you need first
A Zendesk Support trial with a subdomain starting d3v-, converted to a sponsored account
Global OAuth requests are only accepted from d3v- subdomains, and sponsored accounts are reserved for developers building for the Marketplace.
An organization registered on the Zendesk Marketplace developer portal
Both the global OAuth request form and Marketplace submissions live in that portal.
An HTTPS redirect URL and a confidential server to hold the client secret
Confidential clients authenticate with a secret (or PKCE) when exchanging the code; public clients must use PKCE.
Refresh token handling in your token store
New global clients get 30-minute access tokens by default, and Zendesk says refresh support is required for global clients from January 31, 2026.