> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/platform/credentials/api-keys.md).
# API Keys
Overview of API Key in Qubitro, including creation, management, and access control.
API Key allows secure access to Qubitro for building custom applications and integrations.
### Key Features
1. **Expiration Control:** Configure a fixed duration or opt for no expiration.
2. **Granular Permissions:** Assign specific privileges such as Create, Read, Write, Delete, or Invite.
3. **Scoped Access:** Restrict each key to chosen projects.
### Create an API Key
{% stepper %}
{% step %}
**Navigate to API Keys**
On the Qubitro Portal Home Page, select **Credentials** from the top navigation. Then, in the left panel, select **API Keys**.
{% endstep %}
{% step %}
**Create a New API Key**
1. Click on Create API Key. Enter the name, expiration date, and permissions.
2. Enable scope (optional) to limit access to specific projects.
3. Click Create new API Key and copy it immediately for secure storage.
{% hint style="warning" %}
**Warning:** API Keys **cannot** be **edited** or **viewed** again after creation. If lost, delete the key and create a new one.
{% endhint %}
{% endstep %}
{% endstepper %}
### Manage API Keys
#### View API Keys
Created API Keys are listed automatically under API Keys in the Credentials tab. Each key displays its name, scope, assigned actions, and expiration date.
API Keys page in Qubitro Portal displaying existing keys, scopes, permissions, and delete options.
#### Delete an API Key
Click Delete next to the API Key to remove it.
{% hint style="danger" %}
**Warning:** Deleting an API Key immediately revokes its access. This action cannot be undone.
{% 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://docs.qubitro.com/platform/credentials/api-keys.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.
