> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/remove-integration-access/zendesk.md).

# Zendesk: Remove Sprinto Access

Remove the access Sprinto was given in Zendesk. Covers every way Sprinto can be connected to Zendesk and the steps to take in Zendesk for each.

Use this guide to remove the access you gave Sprinto in Zendesk. These steps are done in Zendesk, not in Sprinto.

## Which connection method did you use?

Sprinto can be connected to Zendesk in 3 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                                       | How to tell                                                                                                                   |
| --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| [Access review connection (API token)](#access-review-connection-api-token)             | Zendesk was connected for access review by pasting a Zendesk email address and an API token.                                  |
| [Access review connection (Zendesk sign-in)](#access-review-connection-zendesk-sign-in) | Zendesk was connected for access review by entering the Zendesk subdomain and signing in to Zendesk; no API token was pasted. |
| [Ticketing connection (Zendesk sign-in)](#ticketing-connection-zendesk-sign-in)         | Zendesk was connected as a ticketing system (ticket sync for change or incident evidence) by signing in to Zendesk.           |

***

## Access review connection (API token) <a href="#access-review-connection-api-token" id="access-review-connection-api-token"></a>

**Who must do this:** Zendesk admin

**What gets removed:** The Zendesk API token that was created for Sprinto.

### Steps

1. In Zendesk Admin Center, click **Apps and integrations** in the sidebar, then select **APIs** → **API tokens**. Any admin can do this.
2. Find the token created for Sprinto (check its description and when it was last used).
3. If its status isn't Deactivated, click the options menu (⋯) next to it, select **Deactivate**, then select **Deactivate** in the dialog. Zendesk only lets you delete deactivated tokens.
4. Click the options menu next to the token, select **Delete**, then click **Delete** in the confirmation dialog. This is permanent.

### Confirm it's removed

The token no longer appears under Admin Center → Apps and integrations → APIs → API tokens.

{% hint style="warning" %}
Zendesk is retiring API tokens: unused tokens start auto-deactivating on July 28, 2026, new tokens can't be created from October 27, 2026, and all tokens stop working on April 30, 2027. Reconnect later with the Zendesk sign-in option.
{% endhint %}

**Official guide:** [Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408889192858-Managing-API-token-access-to-the-Zendesk-API)

***

## Access review connection (Zendesk sign-in) <a href="#access-review-connection-zendesk-sign-in" id="access-review-connection-zendesk-sign-in"></a>

**Who must do this:** Zendesk admin (Admin Center access)

**What gets removed:** The OAuth tokens that let Sprinto read users and organizations in your Zendesk account.

### Steps

1. Sign in to Zendesk as an admin and open Admin Center. Any admin can do this, even if the person who connected has left.
2. Click **Apps and integrations** in the sidebar, then select **APIs** → **External OAuth clients**.
3. Find the client Sprinto used. The app may be listed as Sprinto or Truto. Check the company name and the date last used to be sure.
4. Click the options menu (⋯) next to the client and select **View token**.
5. Select all of the client's tokens, click the options menu next to any selected token, select **Delete** and confirm. Deleting every token for the client fully revokes its access.

### Confirm it's removed

The client's token list is empty (or the client no longer appears) under Admin Center → Apps and integrations → APIs → External OAuth clients.

{% hint style="warning" %}
If you also connected Zendesk to Sprinto as a ticketing system, that connection shows as a separate client. Leave it unless you're removing that one too.
{% endhint %}

**Official guide:** [Zendesk help](https://support.zendesk.com/hc/en-us/articles/9447118302362-Managing-external-OAuth-clients)

***

## Ticketing connection (Zendesk sign-in) <a href="#ticketing-connection-zendesk-sign-in" id="ticketing-connection-zendesk-sign-in"></a>

**Who must do this:** Zendesk admin (Admin Center access)

**What gets removed:** The OAuth tokens that let Sprinto read tickets in your Zendesk account.

### Steps

1. Sign in to Zendesk as an admin and open Admin Center. Any admin can do this, even if the person who connected has left.
2. Click **Apps and integrations** in the sidebar, then select **APIs** → **External OAuth clients**.
3. Find the client Sprinto used. The app may be listed as Sprinto or Merge. Check the company name and the date last used to be sure.
4. Click the options menu (⋯) next to the client and select **View token**.
5. Select all of the client's tokens, click the options menu next to any selected token, select **Delete** and confirm. Deleting every token for the client fully revokes its access.

### Confirm it's removed

The client's token list is empty (or the client no longer appears) under Admin Center → Apps and integrations → APIs → External OAuth clients.

{% hint style="warning" %}
If you also connected Zendesk to Sprinto for access review, that connection shows as a separate client. Leave it unless you're removing that one too.
{% endhint %}

**Official guide:** [Zendesk help](https://support.zendesk.com/hc/en-us/articles/9447118302362-Managing-external-OAuth-clients)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/integrations/remove-integration-access/zendesk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
