Palo Alto Networks

Palo Alto Networks Registry API

{'$ref': 'desc/registry/registry.md'}

GitHub OpenAPI
Business capability
Vulnerability Management BC-620.40

Operations 20

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

DELETE /api/v1/registry/webhook/webhook Remove the registry webhook · Delete a Registry Webhook #
Ask an LLM
“How can I turn off the registry webhook so registries stop pushing events?”
“Is there a way to delete the registry webhook configuration entirely?”
Tell an agent destructive · confirm first
Delete the registry webhook.
Remove the webhook that receives registry push events.
POST /api/v1/registry/webhook/webhook Send a registry webhook event · Registry Webhook #
Ask an LLM
“Can a container registry push an event to Prisma Cloud Compute through a webhook?”
“Which fields does the registry webhook accept, like event type, action and domain?”
Tell an agent
Post a registry webhook event of type {event_type} with action {action}.
Notify the registry webhook about an Artifactory push from domain {domain}.
GET /api/v34.03/registry Get registry scan results (v34.03) · Get Registry Scan Results #
Ask an LLM
“Where can I see registry image scan results using the v34.03 API version?”
“Can I filter v34.03 registry scan results by repository and severity?”
Tell an agent
On API v34.03, show registry scan results for repository {repository}.
Fetch v34.03 registry scan findings for image {imageID}.
GET /api/v34.03/registry/download Download registry scan results (v34.03) · Download Registry Scan Results #
Ask an LLM
“Can I export registry scan findings to a file with the older v34.03 endpoint?”
“Is it possible to download v34.03 registry results for only one registry?”
Tell an agent
Download the v34.03 registry scan report for registry {registry}.
Export all registry scan results as a file via API version 34.03.
GET /api/v34.03/registry/names List registry image names (v34.03) · Get Registry Image Names #
Ask an LLM
“What image names has the registry scanner found, per the v34.03 API?”
“Can I get just the image names from registry scans on version 34.03?”
Tell an agent
List scanned registry image names in repository {repository} using v34.03.
Give me only the names of registry images, older v34.03 endpoint.
GET /api/v34.03/registry/progress Check registry scan progress (v34.03) · View Registry Scan Progress #
Ask an LLM
“Is my registry scan still running, according to the v34.03 progress endpoint?”
“How far along is the on-demand registry scan under API v34.03?”
Tell an agent
Show v34.03 scan progress for registry {registry}.
Check how far the v34.03 scan of repo {repo} tag {tag} has gotten.
POST /api/v34.03/registry/scan Start a registry scan (v34.03) · Start a Registry Scan #
Ask an LLM
“Can I kick off a registry scan on demand through the v34.03 API?”
“Could I rescan one tagged image in a registry using version 34.03?”
Tell an agent
Start an on-demand registry scan with the v34.03 API.
Trigger a v34.03 registry scan for tag {tag}.
POST /api/v34.03/registry/scan/select Scan selected registries (v34.03) · Scan Registries #
Ask an LLM
“Can I scan only a chosen set of registries rather than all of them on v34.03?”
“Which v34.03 call scans a selection of registries at once?”
Tell an agent
Scan the selected registries using the v34.03 select endpoint.
Run a v34.03 scan against just the registries I picked.
POST /api/v34.03/registry/stop Stop all registry scanning (v34.03) · Stop a Registry Scan #
Ask an LLM
“Can I halt a running registry scan with the v34.03 API?”
“What stops every in-progress registry scan on version 34.03?”
Tell an agent destructive · confirm first
Stop the running registry scan via v34.03.
Halt all ongoing registry scanning, API version 34.03.
POST /api/v34.03/registry/stop/{id} Stop one registry spec scan (v34.03) · Stop a Registry spec Scan #
Ask an LLM
“Can I stop the scan of just one registry specification on v34.03?”
“Is there a way to cancel a single registry spec scan by its ID in version 34.03?”
Tell an agent destructive · confirm first
Stop the v34.03 registry spec scan {id}.
Cancel scanning of registry specification {id} with API v34.03.
GET /api/v34.04/registry Get registry scan results · Get Registry Scan Results #
Ask an LLM
“What vulnerabilities did the latest registry scans find in my images?”
“Can I narrow registry scan results to one registry and a minimum severity?”
Tell an agent
Show registry scan results for registry {registry}.
Get registry scan findings with severity {normalizedSeverity}, v34.04.
GET /api/v34.04/registry/download Download registry scan results · Download Registry Scan Results #
Ask an LLM
“How do I export registry image scan results as a downloadable file?”
“Can I download registry findings filtered to a single repository in v34.04?”
Tell an agent
Download registry scan results for repository {repository} as a file.
Export the current registry scan report on API version 34.04.
GET /api/v34.04/registry/names List registry image names · Get Registry Image Names #
Ask an LLM
“Which image names exist across my scanned registries?”
“Can I pull a plain list of registry image names without full scan detail on v34.04?”
Tell an agent
List the image names found in registry {registry}.
Return just the names of scanned registry images, latest v34.04 API.
GET /api/v34.04/registry/progress Check registry scan progress · View Registry Scan Progress #
Ask an LLM
“How far along is the current registry scan?”
“Can I check scan progress for one image digest in a registry?”
Tell an agent
Show registry scan progress for digest {digest}.
Report the progress of the on-demand registry scan for repo {repo}, v34.04.
POST /api/v34.04/registry/scan Start a registry scan · Start a Registry Scan #
Ask an LLM
“Can I trigger a registry scan right now instead of waiting for the schedule?”
“Is it possible to scan a single image tag in a registry on demand?”
Tell an agent
Start a registry scan now.
Kick off an on-demand registry scan of tag {tag} on API v34.04.
POST /api/v34.04/registry/scan/select Scan selected registries · Scan Registries #
Ask an LLM
“Can I run a scan across only a few specific registries?”
“What is the call to scan a chosen subset of registries in v34.04?”
Tell an agent
Scan only the registries I selected.
Launch a scan for my picked registries using the current v34.04 API.
POST /api/v34.04/registry/stop Stop all registry scanning · Stop a Registry Scan #
Ask an LLM
“How can I stop a registry scan that is taking too long?”
“Can I abort all registry scans currently in progress on v34.04?”
Tell an agent destructive · confirm first
Stop the registry scan that is running.
Abort every in-progress registry scan with the v34.04 API.
POST /api/v34.04/registry/stop/{id} Stop one registry spec scan · Stop a Registry spec Scan #
Ask an LLM
“Can I stop scanning just one registry specification while others keep going?”
“Is there a call to cancel a registry spec scan by ID on v34.04?”
Tell an agent destructive · confirm first
Stop the scan for registry specification {id}.
Cancel registry spec scan {id} using API version 34.04.
GET /registry List configured registries · Palo Alto Networks List Configured Registries #
Ask an LLM
“Which container registries are set up for scanning in Prisma Cloud Compute?”
“What schedule and scope does each configured registry use?”
Tell an agent
List all container registries configured for scanning.
Show me the registry scanning configuration with credentials and schedules.
POST /registry Add a registry to scanning · Palo Alto Networks Add a Registry #
Ask an LLM
“Can I add a new ECR or Docker Hub registry to be scanned?”
“What do I need to register a container registry for vulnerability scanning?”
Tell an agent
Add registry {registry} of type {version} to the scan configuration.
Register {registry} for scanning using credential {credentialID}, type {version}.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-registry-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/palo-alto-networks:palo-alto-networks-registry-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

palo-alto-networks-registry-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Palo Alto Networks Registry API
  x-refined-note:
  - x-description-source differs across the merged source definitions and was not carried
  version: '1.0'
  description: 'Operations tagged Registry across 3 of this provider''s published API definitions: palo-alto-compute-34-03-openapi-34-03-138-sh-openapi.json, palo-alto-compute-openapi-34-04-145-sh-openapi.json, palo-alto-prisma-cloud-compute-api-openapi-original.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://{console}/api/v1
  description: Prisma Cloud Compute Console API.
  variables:
    console:
      default: console.example.com
      description: Address of the Prisma Cloud Compute Console. For SaaS deployments, use the address provided in Prisma Cloud under Compute > Manage > System > Utilities.
tags:


# --- truncated at 32 KB (150 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-registry-api-openapi.yml