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

# Keka: Remove Sprinto Access

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

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

***

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

**How to tell:** Only option: you created an API key in Keka (Client ID, Client Secret and API key) and pasted them.

**Who must do this:** Keka Global admin (or IT admin)

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

### Steps

1. Sign in to Keka as a Global admin and click the gear icon next to your organisation name to open Global Settings.
2. Go to **Integrations and Automation** → **API Access** → **API Key**.
3. Find the key created for Sprinto by its name or created date.
4. Under Actions, click the three dots and choose **Revoke**, not the option that issues a replacement key.
5. Leave the Client ID and Client Secret alone unless only Sprinto used them; other integrations may depend on them.

### Confirm it's removed

The key no longer shows as active under Global Settings → Integrations and Automation → API Access → API Key.

**Official guide:** [Keka Help: API usage FAQ](https://help.keka.com/hc/en-us/articles/39946809363985-Frequently-Asked-Questions-Keka-API-Usage-and-Integration)


---

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