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

# Creation

To create a new key:

{% stepper %}
{% step %}

### Go to Settings > API keys.

This section contains a list of created API keys and tools for creating and managing them.
{% endstep %}

{% step %}

### Click the Add API key button.

The button opens a form for creating a new API key.

<figure><img src="https://572977165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPbZABdmwpFq6bAJuwUC%2Fuploads%2FfVnsfLMtuItsqTm9Mfez%2FDodawanie%20klucza%20API.png?alt=media&amp;token=7e42eb00-d1b1-4f7d-89f4-766b11d8bbba" alt="Widok zarządzania kluczami API z przyciskiem Add API key."><figcaption><p>Starting the creation of a new API key.</p></figcaption></figure>
{% endstep %}

{% step %}

### Enter a name&#x20;

The name should help easily identify the purpose of the key, e.g. `Outlook`, `eAuditor` or the name of a specific integration. Confirm the name, then click **Create API key**.

<figure><img src="https://572977165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPbZABdmwpFq6bAJuwUC%2Fuploads%2F61Yct43AXTuauv9ygQNX%2FTworzenie%20api%20key%202.png?alt=media&amp;token=a5eeae31-c245-47ef-9a64-daa8d6a4054d" alt="Okno Add API key z polem umożliwiającym wpisanie nazwy nowego klucza." width="534"><figcaption><p>Naming and creating a new API key.</p></figcaption></figure>
{% endstep %}

{% step %}

### Copy the key and finish the process.

After generating the key, click **Copy to clipboard** and save it in a safe place. Then click **Done**, to finish creating the key.

{% hint style="danger" %}
**Important:** The full API key value is displayed only while it is being created. After closing the window, you will not be able to display the full key again. If it is lost, you must generate a new one.
{% endhint %}

<figure><img src="https://572977165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPbZABdmwpFq6bAJuwUC%2Fuploads%2FALsKwA0keXB34Ey23K6r%2FTworzenie%20api%20key%203.png?alt=media&amp;token=2b86319d-25b5-4f93-83a1-28141c234af5" alt="kno z wygenerowaną wartością klucza API oraz przyciskami Copy to clipboard i Done." width="537"><figcaption><p>Copying and saving the generated API key.</p></figcaption></figure>
{% endstep %}
{% endstepper %}


---

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