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

# Security

An API key allows an application or integration to authenticate access to the system. For this reason, it should be treated like a password or other credentials.

{% hint style="danger" %}
**Important:** Do not share the API key with other people, do not send it in email messages or instant messengers, and do not place it in public documents, code repositories, or screenshots.
{% endhint %}

Keys should be stored in a secure location intended for managing secrets or credentials. For different integrations, it is worth creating separate keys and giving them clear names. This makes it easier to later disable access for a specific integration without affecting the other connections.

If there is a suspicion that the key has been disclosed to an unauthorized person, it should be[ **immediately deactivated or deleted and a new one created**.](/en/features/settings/api-keys/management.md)


---

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