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

# SendGrid: Remove Sprinto Access

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

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

***

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

**How to tell:** SendGrid was connected by pasting a SendGrid API key on the sign-in window.

**Who must do this:** SendGrid account owner or a teammate with Full Access to API Keys

**What gets removed:** The SendGrid API key Sprinto used to read your teammates, plus the helper key made during setup.

### Steps

1. Sign in to SendGrid and go to **Settings** → **API Keys** (app.sendgrid.com/settings/api\_keys).
2. Find the key you created for Sprinto (match its name or API Key ID). Click the action menu, then Delete API Key, and click **Confirm**.
3. If you also created a Full Access key during setup only to add the `teammates.read` permission, delete it the same way.
4. If the person who created the key has left, a teammate with Full Access to API Keys can delete it from the same page. Deleting their teammate account does not delete their API keys.
5. Optional: delete any saved copies of the keys.

### Confirm it's removed

The API Keys page no longer lists the key(s); SendGrid rejects calls made with them.

**Official guide:** [Twilio SendGrid docs](https://www.twilio.com/docs/sendgrid/ui/account-and-settings/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/sendgrid.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.
