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

# Semgrep: Remove Sprinto Access

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

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

***

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

**How to tell:** Only one way to connect: an organization slug and API token pasted into Sprinto's Semgrep form.

**Who must do this:** Semgrep deployment admin

**What gets removed:** The Semgrep API token Sprinto used to read findings.

### Steps

1. Sign in to Semgrep AppSec Platform as an admin (any admin works, even if the person who created the token has left) and pick the organization from the drop-down at the top left.
2. Go to **Settings** → **Tokens** → **API tokens**.
3. Find the token created for Sprinto (filter the scope drop-down by Web API if needed) and click **Revoke**.
4. Optional: delete any saved copies of the token's Secrets value.

### Confirm it's removed

The token no longer appears in the API tokens list.

**Official guide:** [Semgrep docs](https://docs.semgrep.dev/deployment/tokens)


---

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