> 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-xsiam/cloud-security/container-registry-scanning/manage-registry-scanning-with-apis.md).

# Manage registry scanning with APIs

Learn how to onboard and manage registry scanning programatically with APIs for Cortex XSIAM.

### 1. Onboarding and managing connectors

#### Third-party integrations

Use the [registry onboarding API](https://cortex-docs.paloaltonetworks.com/xsiam-api/cloud-workload-protection/registry-onboarding) endpoints to onboard or manage third-party integrations such as JFrog Artifactory, Docker Hub, Harbor, Sonatype Nexus, GitLab Container Registry, Docker V2, and OpenShift.

Cortex provides dedicated, schema-validated Public API endpoints:

<table><thead><tr><th width="188.8876953125">Action</th><th>Endpoint</th></tr></thead><tbody><tr><td>Create connector</td><td><code>POST /public_api/v1/cwp/registry_onboarding/instances</code></td></tr><tr><td>Get connector details</td><td><code>GET /public_api/v1/cwp/registry_onboarding/instances/{connectorID}</code></td></tr><tr><td>Update connector</td><td><code>PUT /public_api/v1/cwp/registry_onboarding/instances/{connectorID}</code></td></tr><tr><td>Delete connector</td><td><code>DELETE /public_api/v1/cwp/registry_onboarding/instances/{connectorID}</code></td></tr></tbody></table>

#### Managed cloud registries

(AWS ECR, GCP Artifact Registry/GCR, Azure ACR, OCI)

No individual registry-creation endpoints. These are onboarded at the cloud account level through [Cloud Account Onboarding APIs](https://cortex-docs.paloaltonetworks.com/xsiam-api/cloud-onboarding/cloud-onboarding-overview).

### 2. Triggering scans

There is no public API to trigger on-demand registry scans. Registry scanning is automated and event-driven.

### 3. Retrieving scan results

There's no single dedicated `/public_api/.../registry/scan-results` endpoint. Because results are normalized into the Unified Asset Inventory, findings, and issues, you retrieve them as follows:

a. [Asset SBOM API](https://cortex-docs.paloaltonetworks.com/xsiam-api/cloud-workload-protection/sbom)

* `GET /public_api/v1/assets/{assetId}/sbom` — returns the SBOM (packages, versions, licenses) for a scanned container image asset.

b. [XQL Query API](https://cortex-docs.paloaltonetworks.com/xsiam-api/cortex-platform/xql-query)

* `POST /public_api/v1/xql/start_xql_query` and `POST /public_api/v1/xql/get_query_results`
  * Image assets & metadata: query the `asset_inventory` dataset filtered on the container image asset type to inspect tags, digests, repositories, registries, and scan timestamps.
  * Vulnerabilities, secrets, malware: query the `findings` dataset by asset ID, for finding types such as `VULNERABILITY`, `MALWARE`, `SECRET`, or compliance checks.

c. [Platform Issues API](https://cortex-docs.paloaltonetworks.com/xsiam-api/issues-apis/issues-apis-overview)

* `POST /public_api/v1/issue/search/` and `GET /public_api/v1/issue/<issue_id>/` — retrieves security issues generated when scanned images trigger CWP security policies.


---

# 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/cortex-xsiam/cloud-security/container-registry-scanning/manage-registry-scanning-with-apis.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.