> 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/freshservice.md).

# Freshservice: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in Freshservice. These steps are done in Freshservice, not in Sprinto. To connect Freshservice to Sprinto again later, see [Freshservice Integration (Access Review)](https://docs.sprinto.com/integrations/overview/freshservice-integration-access-review.md) or [Freshservice Integration (Ticketing and Incident Management)](https://docs.sprinto.com/integrations/overview/freshservice-integration-ticketing-and-incident-management.md).

## Which connection method did you use?

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

| Connection method                                                     | How to tell                                                                                                                                                                      |
| --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [API key from an integration user](#api-key-from-an-integration-user) | Freshservice was connected with the API key of an integration user (a non-login system account under Global Settings → User Management → Integration Users), not a person's key. |
| [API key from an agent's profile](#api-key-from-an-agents-profile)    | Freshservice was connected (for access review or ticket sync) with the API key shown in a person's Freshservice Profile settings.                                                |

***

## API key from an integration user <a href="#api-key-from-an-integration-user" id="api-key-from-an-integration-user"></a>

**Who must do this:** Freshservice admin with the **Reset API key for integration users** permission

**What gets removed:** The integration user's API key that Sprinto holds, by replacing it with a new one.

### Steps

1. Sign in to Freshservice as an admin with the Reset API key for integration users permission. This works even if the person who set it up has left.
2. Go to **Admin** → **Global Settings** → **User Management** → **Integration Users** and open the integration user created for Sprinto.
3. In the **API key** card, click the More options (⋯) menu and click **Reset API key**.
4. In the confirmation dialog, click **Reset API key**. Freshservice has no delete for API keys; resetting permanently invalidates the key Sprinto holds.

### Confirm it's removed

The key shown in the integration user's API key card has changed.

{% hint style="warning" %}
Freshservice can't delete an API key or an integration user, only reset the key. Anything else using this integration user's key stops working until you give it the new key.
{% endhint %}

**Official guide:** [Freshservice support](https://support.freshservice.com/support/solutions/articles/50000014413-manage-integration-users-in-freshservice)

***

## API key from an agent's profile <a href="#api-key-from-an-agents-profile" id="api-key-from-an-agents-profile"></a>

**Who must do this:** The agent whose API key was used; a Freshservice admin who manages agents if that person has left

**What gets removed:** The agent API key Sprinto holds, by replacing it with a new one.

### Steps

1. Sign in to Freshservice as the agent whose API key was used. If both the access review and ticketing connections were set up, do this for each agent whose key was used.
2. Click your profile picture (top right) and go to Profile settings.
3. Find your API key on the right, below Delegate Approvals, and confirm your identity if Freshservice asks.
4. Click **Reset API Key** and confirm. Freshservice has no delete for API keys; resetting permanently invalidates the key Sprinto holds.
5. If that agent has left: an admin goes to **Admin** → **Global Settings** → **User Management** → **Agents**, opens the agent, clicks the more options menu and selects Forget User. This permanently removes the agent and also deletes the incidents, notes and service requests they created, so check first.

### Confirm it's removed

The API key shown in the agent's Profile settings has changed (or the agent no longer appears under Admin → Global Settings → User Management → Agents).

{% hint style="warning" %}
Freshservice can't delete an API key, only reset it. Any other app, script or Sprinto connection using this key stops working until you give it the new key.
{% endhint %}

{% hint style="info" %}
The reset button may be labelled differently in your account (for example **Reset API Key**). If you use **Forget User** instead, check that the old key no longer works.
{% endhint %}

**Official guide:** [Freshservice support](https://support.freshservice.com/support/solutions/articles/50000000306-where-do-i-find-my-api-key-)


---

# 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/freshservice.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.
