I will migrate your zendesk API token integrations to oauth


About this gig
Zendesk is retiring API tokens. Since October 27, 2026 accounts can no longer create new ones, and on April 30, 2027 every remaining token stops working. Scripts, webhooks and integrations that still sign in with a token will start getting authentication errors.
I move them to OAuth before that date.
First I find what still uses tokens. The API tokens page in Admin Center shows when each token was last used, and the usage report shows which scripts call the API. Then I rewrite the authentication in your code to OAuth, so it gets new access tokens on its own. For webhooks that call your own Zendesk, I check whether an action flow can replace them.
I work in Python and Node.js. You get the updated code, a short test you can run, and a list of tokens that are safe to delete.
I never ask for your Zendesk password. You share the code with keys removed, and I walk you through creating the OAuth client in Admin Center.
Get to know Ruslan
AI Engineer, LLM Apps, RAG and Document AI
- FromAzerbaijan
- Member sinceNov 2026
Languages
Azerbaijani, Russian, English
FAQ
Which integrations are affected?
Anything that calls the Zendesk Ticketing, Help Center or Voice API with an API token: your own scripts, middleware, integrations built by a contractor, webhooks that call back into Zendesk. Marketplace apps already have to use OAuth.
Do I need to give you admin access?
No. You send the code with keys removed and a screenshot of the API token usage report. I explain each click in Admin Center, and you create the OAuth client yourself.
One of my tokens was already deactivated. Can you still help?
Yes. Tokens unused for 30 days started getting deactivated on July 28, 2026. The fix is the same: switch that integration to OAuth.
My integration is not in Python or Node.js. What then?
Message me before ordering with a short piece of the code. I'll tell you honestly whether I can do it.
