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

# Datadog: Remove Sprinto Access

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

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

***

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

**How to tell:** Both Datadog connections in Sprinto (infrastructure monitoring & incidents, and access review) use an API key plus an application key and a region.

**Who must do this:** Datadog Admin role (API Keys Delete and Org App Keys Write permissions); or the application key owner

**What gets removed:** The Datadog API key and application key created for Sprinto.

### Steps

1. Sign in to Datadog on your site (for example app.datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, app.datadoghq.eu, ap1.datadoghq.com or app.ddog-gov.com) and go to **Organization Settings** → **Application Keys**.
2. Search for the application key created for Sprinto (often named `Sprinto Access`) and click **Revoke** next to it. Admins can find keys owned by any user, including people who have left.
3. If the key belongs to a service account: go to **Organization Settings** → **Service Accounts**, open the account, hover over the key, click the trash can icon and then **Confirm**.
4. Go to **Organization Settings** → **API Keys**, find the API key created for Sprinto and click the **Revoke** icon next to it. Do not click **Unrevoke**; it is permanently removed after 7 days.
5. If you connected both Datadog connections with different key pairs, repeat steps 2–4 for the second pair.
6. Optional: delete any saved copies of the keys (password manager, notes, secrets store).

### Confirm it's removed

The application key is gone from Application Keys (or the service account's keys) and the API key shows Revoked in API Keys. Reconnecting only needs a new key pair.

{% hint style="warning" %}
Revoke only keys created for Sprinto. API keys are shared across the organization: if you gave Sprinto an existing API key that your Datadog Agents or other tools use, they stop sending data. If you used the same keys for both Datadog connections in Sprinto, revoking them stops both.
{% endhint %}

**Official guide:** [Datadog docs](https://docs.datadoghq.com/account_management/api-app-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/datadog.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.
