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

# What's new in this release

* [What's new in this release](#whats-new-in-this-release)
  * [Cortex Xpanse 2.14](#cortex-xpanse-214)
  * [Earlier changes](#earlier-changes)

<br>

## Cortex Xpanse 2.14

| Product Name             | Details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cortex Xpanse Public API | <p><strong>API reference published</strong><br>The Cortex Xpanse REST API reference is now published in the Cortex API documentation portal, covering 46 endpoints across the following areas: Asset Management, Attack Surface Rules, Audit Log, Authentication Settings, Incident Management, Remediation Path Rules, Remediation Scanning, System Management, Tag Management, and Vulnerability Testing.<br><br><strong>Updated Schemas</strong><br>- <code>AssignOrRemoveTagsFromAsmAssetsRequestFilter</code>: Added the missing <code>value</code> property, added <code>value</code> to the <code>required</code> array, and corrected the <code>field</code> and <code>operator</code> descriptions. Requests that assign or remove tags on assets must include <code>value</code> in each filter.</p> |

<br>

## Earlier changes

| Endpoint                                      | Name             | Notes                                                                   |
| --------------------------------------------- | ---------------- | ----------------------------------------------------------------------- |
| `/public_api/v1/assets/get_external_services` | Get All Services | CPE data fields are now included in the Get All Services call response. |


---

# 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/xpanse-api/changes-to-the-api-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.