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

# incident.io: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in incident.io. These steps are done in incident.io, not in Sprinto. To connect incident.io to Sprinto again later, see [Incident.io Integration](https://docs.sprinto.com/integrations/overview/incident.io-integration.md).

***

## API key <a href="#api-key" id="api-key"></a>

**How to tell:** You pasted an incident.io API key into Sprinto's incident management setup.

**Who must do this:** incident.io user with the Manage API keys permission (for example an Admin or Owner)

**What gets removed:** The incident.io API key Sprinto uses.

### Steps

1. Sign in to incident.io and go to **Settings** → **API keys**.
2. Find the key you made for Sprinto by its name.
3. Delete the key and confirm.
4. If the key isn't there, check the **User keys** tab on the same page. Admins can search by key name or owner and delete user keys there too.

### Confirm it's removed

The key no longer appears under Settings → API keys.

**Official guide:** [incident.io docs](https://docs.incident.io/admin/api-keys)


---

# 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/incident-io.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.
