Connect Zendesk with an API token
The fallback way to connect Zendesk with an existing agent API token, and why Zendesk is switching these tokens off.
Most people connect Zendesk by signing in: see Zendesk. This article is for the fallback: connecting with a Zendesk API token you already have.
Zendesk stopped creating new API tokens on 27 October 2026 and switches existing ones off on 30 April 2027. Tokens unused for 30 days already stop working, and Zendesk accounts created since 28 July 2026 can't use tokens. Use this only if you have a token that's still active; otherwise use Sign in with Zendesk.
When you'd use a token
- You have an active Zendesk API token and prefer to use it.
- Sign in with Zendesk isn't available. The Connect Zendesk page then shows Connect with an existing API token with the note Zendesk sign-in isn't set up on this server, so connect with a token you already have.
What you need
- Your Zendesk address (the part before
.zendesk.com). - An active Zendesk API token.
- The email address of the agent your AI should act as. Its actions appear in Zendesk as that agent. It must be an agent or admin, not an end user.
Connect with a token
- In app.plugsight.app, go to Connections and click Add connection.
- Click the Zendesk tile.
- If you see Sign in with Zendesk, open Have an older Zendesk API token? (most people don't need this) below it.
- In Your Zendesk address, type the part before
.zendesk.com. - Optional: type a Name, for example "Support desk".
- Type the agent's email address in Agent email.
- Paste the token into API token.
- Click Test connection & save.
Plugsight checks the token with Zendesk before saving anything. You then see a message such as Connected yourcompany.zendesk.com as Jane Smith (agent), id "support-desk".
Once connected, a token connection works exactly like a signed-in one: the same actions, the same Can reply & update switch and the same approval in the chat. See Zendesk.
Moving from a token to sign-in
Before your token stops working, connect the same Zendesk again with Continue with Zendesk, signing in as the same agent. Plugsight recognises the same agent on the same Zendesk and replaces the token with the sign-in, keeping your settings. The message then says Reconnected.
Troubleshooting
Could not connect: Zendesk rejected the credentials. Check the agent email and API token. Zendesk no longer issues new tokens, so use Sign in with Zendesk if this one was removed.
What it means: Zendesk didn't accept the email and token together. The token may be mistyped, switched off, unused for over 30 days, or belong to another Zendesk.
How to fix it: check the agent email and token. If the token no longer works, connect with Sign in with Zendesk instead: Zendesk won't issue a new token.
Could not connect: That Zendesk user isn't an agent. Use an agent or admin account.
What it means: the email belongs to an end user (customer).
How to fix it: use the email of an agent or admin.
Enter your Zendesk address, like yourcompany.zendesk.com.
What it means: Your Zendesk address was empty or couldn't be read.
How to fix it: type the part before .zendesk.com, for example yourcompany.
The connection says it needs reconnecting: "Zendesk rejected the API token."
What it means: a token that was working has stopped, for example because it was switched off or went unused for 30 days.
How to fix it: connect again with Sign in with Zendesk, as the same agent. See Moving from a token to sign-in.