> 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/changes-in-this-release.md).

# Changes in this release

## New Paths

### `POST /public_api/v1/system_diagnostics/data/papi/`

**Note:** This endpoint is supported in XSOAR 8.13 On-prem and later.

| Property         | Value                                                               |
| ---------------- | ------------------------------------------------------------------- |
| **Operation ID** | `getSystemHealthMetrics`                                            |
| **Tag**          | System Management                                                   |
| **Summary**      | Get System Health Metrics                                           |
| **Request body** | None                                                                |
| **Auth**         | `authorization` (api\_key) + `x-xdr-auth-id` (api\_key\_id) headers |
| **Availability** | Cortex XSOAR 8.13 On-prem and later                                 |

**Description:** Retrieves system health metrics snapshots for the tenant. Each snapshot contains node metrics, component statuses, storage usage, queue depths, and external connectivity information. By default, returns data from the last 24 hours. Snapshots are ordered by timestamp descending (most recent first).

**Response codes:**

| Code  | Description                                       |
| ----- | ------------------------------------------------- |
| `200` | Successful response → `SystemDiagnosticsResponse` |
| `400` | Bad Request — invalid JSON                        |
| `401` | Unauthorized — authentication failure             |
| `402` | Unauthorized — insufficient license               |
| `403` | Forbidden — insufficient RBAC permissions         |
| `500` | Internal server error                             |

***

## New Schemas

| Schema                      | Type   | Description                                                                                                           |
| --------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------- |
| `SystemDiagnosticsResponse` | object | Top-level response wrapper with `reply` → `SystemDiagnosticsResults`                                                  |
| `SystemDiagnosticsResults`  | object | Contains `results` array of snapshots                                                                                 |
| `SystemDiagnosticsSnapshot` | object | Point-in-time snapshot: `timestamp`, `nodes`, `cluster_disk_usage`, `components`, `storage`, `queues`, `connectivity` |
| `NodeMetrics`               | object | Per-node health: `name`, `cpu_usage`, `memory_usage`, `os_disk_usage`, `connected`                                    |
| `ConnectivityStatus`        | object | External connectivity: `connected`, `since`, `error`                                                                  |

**Note:** The `ErrorResponse` schema (used by 400/401/402/403/500 responses) already existed in the baseline spec.


---

# 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/xsoar-8-api/changes-in-this-release.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.