> 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/cortex-cloud-posture-management/cloud-inventory-and-environment/asset-classes/api-assets.md).

# API assets

The API asset inventory provides an overview of API assets across cloud providers and data sources, enabling you to analyze, assess, and implement security measures to safeguard against risks.

### API visibility and asset categories

Cortex Cloud observes API traffic and extracts API specification files from gateways. The inventory includes:

* **Endpoints:** Live API endpoint paths used by applications to communicate with servers.
* **Specifications:** OpenAPI or Swagger specification files that are imported or extracted from gateways. You can use Cortex Cloud to validate live traffic against these specifications to alert on surface deviations or undocumented endpoints.

### Expanded API endpoint information

When you click on a specific API endpoint, a side card opens containing detailed information organized into the following tabs

* **Overview:** This tab shows the highlights and properties of the API endpoint. It includes identifying information such as the Asset ID, Provider, and Cloud Region, related Business Applications, and a Relations graph showing the connections between the API endpoint, API gateway, and VMs.
* **Compliance:** This tab displays the asset's overall compliance score and a breakdown of security controls to help you ensure the API aligns with assigned security standards.
* **Endpoint Data:** This tab shows the details of the API endpoint, and the components associated with authentication, such as token type, request/response body schema, and usage statistics. It provides deep visibility into the following areas:
  * **Endpoint metrics:** Displays the Request Content Type, Response Content Type, the total number of Inspected Transactions, and timestamps for First Observed, Last Observed, and Last Changed.
  * **Authentication:** Displays a detailed table of detected authentication methods, including the Type (e.g., OAuth, Basic, API Key, Learning, OIDC), Token Type (e.g., Opaque, Base64, JWT), the Location in the payload (e.g., Query Parameters, Authentication Header), and its Status (e.g., Found, Not Found).
  * **Request Body Schema and Response Body Schema:** Displays the JSON structure, format, and expected data types for both the inbound requests and outbound responses.
  * **Usage Statistics:** Provides graphical bar charts to assess usage patterns, displaying distributions for Requests size distribution, Response size distribution, and Status code distribution.


---

# 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/cortex-cloud-posture-management/cloud-inventory-and-environment/asset-classes/api-assets.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.
