- Home
- Skills
- APIs & Backend
- Zendesk API Token -> OAuth Migration Scanner
Zendesk API Token -> OAuth Migration Scanner
Find every Zendesk API-token auth (email/token Basic auth, Zenpy, node-zendesk, committed tokens) in your code and get the OAuth replacement before tokens stop on Oct 27, 2026 and die on Apr 30, 2027.
Free
Works with the AI Agents you already use
About this skill
Zendesk's schedule (checked 2026-10-24):
- 2026-07-28: tokens unused for 30 days are auto-deactivated, then deleted after a further 60 days. Accounts created from this date cannot use tokens.
- 2026-10-27: no new API tokens can be created.
- 2027-04-30: every Support API token (Ticketing, Help Center, Voice) is deactivated. They cannot be reactivated and no extensions are given.
Token use is reported as WARN, then as ERROR once a deadline is 30 days away or less. Code that creates tokens is ERROR now (the creation stop is 3 days away). Committed tokens are always ERROR, and the scanner masks their values. The scanner exits with code 1 when any ERROR is found.
| Today (API token) | OAuth replacement |
|---|---|
Authorization: Basic base64(email/token:TOKEN) / auth=(f"{email}/token", token) | Authorization: Bearer <access_token> |
| Server job or integration with no user present | client_credentials grant: POST /oauth/tokens with client_id, client_secret and scope. Confidential clients only. No refresh token, so request a new token when the old one expires. Actions are attributed to the user who created the client. |
| An app acting for a user | authorization_code: /oauth/authorizations/new, then POST /oauth/tokens. Public clients must use PKCE. |
| Tokens never expired | Access tokens last 30 min by default (configurable 5 min to 48 h). Refresh tokens last 30 days by default (7 to 90 days). Refresh tokens rotate, so save the new one immediately. |
| Token works on every endpoint | Scopes such as tickets:read or users:write (default "read write"). Allowed scopes are a ceiling: asking for more returns 400 invalid_scope, and using a token outside its scopes returns 403. |
POST /api/v2/api_tokens (token rotation) | Create an OAuth client in Admin Center > Apps and integrations > APIs > OAuth clients |
| Legacy OAuth client (created before 2026-04-30) | Send expires_in to receive refresh tokens |
| Expired credentials | 401 {"error":"invalid_token"} means refresh the token, or request a new one with client_credentials |
| Webhooks that call back using API tokens | Move to action flows or middleware. Zendesk promises native OAuth for webhooks but gives no date. |
| Marketplace apps using customer credentials | Not allowed. Use the app framework's own auth. |
Zenpy token= / node-zendesk token: | Pass the OAuth access token instead. The library option names were not verified on Zendesk docs, so check your library version. |
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 23 days ago
- Free with an Agensi account
- Software
Node.js
Permissions
Allowed Hosts