> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/features/settings/api-keys/management.md).
# Management
The list of keys contains:
* the key name;
* the abbreviated key value;
* creation date;
* status;
* available actions.
For security reasons, the full value of a key created earlier is not displayed again.
### Activation and deactivation
Each key has a status toggle.
A key with status **Active** can be used by the assigned integration. Turning off the switch deactivates the key and prevents further use of it until it is reactivated.
Deactivation is useful when you want to temporarily disable access without permanently deleting the key.
Changing the active status of an API key.
### Editing the key name
Click the pencil icon next to the selected key to change its name.
Changing the name is only for organizing the list and does not change the key's value or its operation.
Editing the name of an existing API key.
### Searching and filtering
Field **Search** allows you to search for keys by their names.
Using the **Filters** you can further narrow the list based on the key status, e.g. display only active or inactive keys.
Searching and filtering API keys.
### Deleting an API key
To permanently delete a key, click the trash icon next to the selected item.
The system will display a confirmation dialog. Click **Accept**, to finish the operation, or **Cancel**, to cancel it.
Removing an API key from the list.
{% hint style="danger" %}
**Important:** The deleted key stops working and cannot be restored. Integrations using this key will lose the ability to authenticate. Before deleting, make sure the key is no longer in use.
{% endhint %}
---
# 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://bluurdoc.bluur.ai/en/features/settings/api-keys/management.md?ask=&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.
