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

# Opsgenie: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                                             | How to tell                                                                            |
| ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| [Opsgenie moved to Jira Service Management or Compass](#opsgenie-moved-to-jira-service-management-or-compass) | Your Opsgenie account has been migrated, so API Key Management is no longer available. |
| [API key](#api-key)                                                                                           | You pasted an Opsgenie API key and chose a region (Default or EU) in Sprinto.          |

***

## Opsgenie moved to Jira Service Management or Compass <a href="#opsgenie-moved-to-jira-service-management-or-compass" id="opsgenie-moved-to-jira-service-management-or-compass"></a>

**Who must do this:** The Atlassian user who created the token, or an organization admin (Atlassian Guard)

**What gets removed:** Any Atlassian API token created for Sprinto after the move.

### Steps

1. Sign in at <https://id.atlassian.com/manage-profile/security/api-tokens> as the person who set up the connection.
2. Select **Revoke** next to any token created for Sprinto and confirm.
3. If that person has left and your organization has Atlassian Guard: an organization admin goes to admin.atlassian.com → **Insights** → **API token activity** and selects Revoke for the token.

### Confirm it's removed

No token for Sprinto remains at id.atlassian.com → Security → API tokens or in Insights → API token activity.

{% hint style="warning" %}
Opsgenie support ends April 5, 2027. After migration, API Key Management is replaced by Atlassian authentication.
{% endhint %}

{% hint style="info" %}
After you finish, check that no older Opsgenie API key created for Sprinto is still listed, and delete it if it is.
{% endhint %}

**Official guide:** [Atlassian docs](https://support.atlassian.com/opsgenie/docs/feature-changes-and-deprecations-in-jira-service-management/)

***

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

**Who must do this:** Opsgenie account owner or admin

**What gets removed:** The Opsgenie API key created for Sprinto.

### Steps

1. Sign in to Opsgenie as an account owner or admin (EU accounts use the EU site).
2. Go to **Settings** → **App Settings** → **API Key Management**.
3. Find the key created for Sprinto (match the name you gave it) and delete it from its row.
4. Optional: delete any saved copies of the key. This doesn't affect reconnecting.

### Confirm it's removed

The key no longer appears in Settings → API Key Management.

{% hint style="warning" %}
Opsgenie support ends April 5, 2027. After that Opsgenie shuts down and data not moved to Jira Service Management is deleted.
{% endhint %}

{% hint style="info" %}
Look for a delete option on the key's row in **API Key Management**.
{% endhint %}

**Official guide:** [Opsgenie docs](https://support.atlassian.com/opsgenie/docs/api-key-management/)


---

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