> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/api-keys.md).

# API Keys

Generate, manage, revoke, and secure API keys for Cortex XSOAR 6.15 REST API access.

The Cortex XSOAR API is organized around REST and uses standard HTTP response codes, authentication, and verbs. The API has predictable, resource-oriented URLs, accepts form-encoded request bodies, and returns JSON-encoded responses.

The Cortex XSOAR API enables you to send requests to the Cortex XSOAR server. Through the API, you can create incidents, download files, complete tasks, add widgets, and more. HTTP requests can be sent using any HTTP client. Requests must include the API Key.

{% hint style="info" %}
View the [Cortex XSOAR API Guide](https://cortex-docs.paloaltonetworks.com/xsoar-6-api/) or download from the **API Keys** page in the UI.
{% endhint %}

### API Key Permissions

API keys inherit the roles and permissions of the user who created the key. If the user's roles or permissions are changed, those changes are applied to the API keys created by the user. Keys can be created from Settings → Integrations → **API Keys**.

From Cortex XSOAR v6.8, you can restrict who can create API keys. Navigate to Settings → Users and Roles → **Roles**. To restrict a role from creating or revoking API Keys, change the API Keys setting to **Read** instead of **Read/Write**.

### API Key Removal

Any user with read/write permissions for API Keys can revoke API Keys via the UI from Settings → Integrations → **API Keys**. Users can also revoke API Keys by sending **`POST /apikeys/revoke/user/{`*****`username`*****`}`**. If a user is locked out/disabled or deleted, the API key is revoked.

### API Key Expiration

API Keys do not automatically expire.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/api-keys.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 `build a script that syncs our docs to a CMS` 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.