> 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.13/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/api-keys.md).

# API Keys

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" %}

### Note

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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/api-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.