> 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-8-api/get-started-with-cortex-xsoar-8-apis.md).

# Get started with Cortex XSOAR 8.x APIs

[Cortex XSOAR](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-docs/) is a comprehensive security orchestration, automation and response (SOAR) platform that unifies case management, automation, real-time collaboration and threat intel management to serve security teams across the incident lifecycle. Using the Cortex XSOAR APIs, you can integrate Cortex XSOAR with third-party apps or services. The APIs allow you to create and search for incidents, search for indicators, and retrieve a widget's statistics.

Before you can begin using Cortex XSOAR APIs, you must generate the following items from Cortex XSOAR:

| Value          | Description                                                                                                                                                                                                                                      |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **API Key**    | The API Key is your unique identifier used as the `Authorization:{key}` header required for authenticating API calls. Depending on your desired security level, you can generate two types of API keys, Advanced or Standard, from Cortex XSOAR. |
| **API Key ID** | The API Key ID is your unique token used to authenticate the API Key. The header used when running an API call is `x-xdr-auth-id:{key_id}`.                                                                                                      |
| **FQDN**       | The FQDN is a unique host and domain name associated with each tenant.                                                                                                                                                                           |

Cortex XSOAR API URIs are made up of your tenant's FQDN, the API name, and endpoint path. For example, `https://api-{fqdn}/xsoar/public/v1/{endpoint_path}/.`

> #### Note
>
> In Cortex XSOAR OPP, you must add a DNS record that points the Cortex XSOAR DNS name that is mapped to the API IP address. For example, `api-xsoar.mycompany.com`.

The following steps describe how to generate the necessary key values and run your first API call:

1. [Create a new API key](/xsoar-8-api/create-a-new-api-key.md).
2. [Get your Cortex XSOAR API key ID](/xsoar-8-api/get-your-cortex-xsoar-api-key-id.md).
3. [Get your FQDN](/xsoar-8-api/get-your-fqdn.md).
4. [Make your first API call](/xsoar-8-api/make-your-first-api-call.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 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-8-api/get-started-with-cortex-xsoar-8-apis.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.