> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/developer-tools/cerby-api/delete-an-api-key.md).

# Delete an API key

This article describes how to delete an active API key.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, and **Admins**
* API key **Owners**
* Only supported using the Cerby web app
  {% endhint %}

As a workspace **Owner**, **Super Admin**, or **Admin**, or as an API key **Owner**, you can delete an API key to permanently revoke its access.

{% hint style="danger" %}
**IMPORTANT:** When you delete an API key, all access and associated functionality is revoked immediately. Update any services or applications that use this key before deleting it.
{% endhint %}

To delete an API key, complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Select the **Settings** option from the left menu. The **Workspace Configuration** page is displayed.
3. Select the **API keys** left tab.
4. Click the **More options** (...) icon for the key you want to delete. A drop-down list is displayed.
5. Select the **Delete API key** option from the list. The **Delete API key?** dialog box is displayed.
6. Click the **Delete API key** button. The dialog box closes and the key appears in the table with the **Removed** status.


---

# 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://help.cerby.com/developer-tools/cerby-api/delete-an-api-key.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.