> 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/xdr-5-api/readme.md).

# Get started with Cortex XDR 5.x APIs

Using the Cortex XDR APIs, you can integrate [Cortex XDR](https://cortex-docs.paloaltonetworks.com/cortex-xdr-docs/) with third-party apps or services to ingest alerts, manage incidents, and perform response actions programmatically. The APIs let you build integrations that extend Cortex XDR across your detection and response workflows.

Before you can begin using Cortex XDR APIs, you must generate the following items in Cortex XDR:

| 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 XDR. |
| **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 XDR API URIs are made up of your tenant's FQDN, the API name, and endpoint path. For example, `https://api-{fqdn}/XDR/public/v1/{endpoint_path}/.` All API calls must be made over HTTPS.

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

1. [Create a new API key](/xdr-5-api/create-a-new-api-key.md).
2. [Get your Cortex XDR API key ID](/xdr-5-api/get-your-cortex-api-key-id.md).
3. [Get your FQDN](/xdr-5-api/get-your-fqdn.md).
4. [Make your first API call](/xdr-5-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 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/xdr-5-api/readme.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.