Palo Alto Networks Dashboard API
The Dashboard API from Palo Alto Networks — 11 operation(s) for dashboard.
The Dashboard API from Palo Alto Networks — 11 operation(s) for dashboard.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/palo-alto-networks-dashboard-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Palo Alto Networks Dashboard API
version: '1.0'
description: 'Operations tagged Dashboard across 3 of this provider''s published API definitions: palo-alto-code-dashboard-openapi.json, palo-alto-prisma-airs-redteam-data-plane-dp-openapi-openapi.yaml, palo-alto-prisma-airs-redteam-management-mp-openapi-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.prismacloud.io
- url: https://api.sase.paloaltonetworks.com/ai-red-teaming/data-plane
- url: https://api.sase.paloaltonetworks.com/ai-red-teaming/mgmt-plane
tags:
- name: Dashboard
paths:
/code/api/v2/dashboard/common-errors-by-policy:
post:
description: 'Gets the list of policies that have the highest number of errors (open issues) and their respective error counts. The response also includes policy details such as `remediationIds` and `severity`.
You can set the `repositories`, `codeCategories`, and `severities` parameters in the request body to filter the results.'
operationId: get dashboard common errors by policy data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/CommonErrorsByPolicyRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/CommonErrorsByPolicyResponse'
description: Common Errors By Policy
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get common errors by policy
security:
- CustomAuthorizer: []
summary: Common Errors By Policy
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/common-errors-by-policy\"\n\npayload = {\n \"codeCategories\": [\"iac\"],\n \"repositories\": [\"string\"],\n \"severities\": [\"INFO\"],\n \"size\": 0\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/common-errors-by-policy \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"codeCategories\":[\"iac\"],\"repositories\":[\"string\"],\"severities\":[\"INFO\"],\"size\":0}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/errors-by-severity:
post:
description: 'Gets a count of issues detected at each severity level.
You can set the `repositories`, `codeCategories`, and `severities` parameters in the request body to filter the results.'
operationId: get dashboard errors by severity data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorsBySeverityRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorsBySeverityResponse'
description: Errors By Severity
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get errors by severity
security:
- CustomAuthorizer: []
summary: Code Issues by Severity
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/errors-by-severity\"\n\npayload = {\n \"codeCategories\": [\"iac\"],\n \"repositories\": [\"string\"],\n \"severities\": [\"INFO\"],\n \"size\": 0\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/errors-by-severity \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"codeCategories\":[\"iac\"],\"repositories\":[\"string\"],\"severities\":[\"INFO\"],\"size\":0}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/iac-errors-by-category:
post:
description: 'Gets the count for each type of IaC misconfiguration issue detected.
The IaC misconfiguration types are:
- IAM
- Logging
- Monitoring
- Networking
- Kubernetes
- General
- Serverless
- Elasticsearch
- Storage
- Public
- Compute
- Drift
You can set the `repositories` and `severities` parameters in the request body to filter the results.<br/>'
operationId: get dashboard iac errors by category data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/IaCErrorsByCategoryRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/IaCErrorsByCategoryResponse'
description: IaC Errors By Category
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get iac errors by category
security:
- CustomAuthorizer: []
summary: IaC Errors by Category
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/iac-errors-by-category\"\n\npayload = {\n \"repositories\": [\"string\"],\n \"severities\": [\"INFO\"],\n \"size\": 0\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/iac-errors-by-category \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"repositories\":[\"string\"],\"severities\":[\"INFO\"],\"size\":0}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/package-licenses:
post:
description: "Gets the list of non-compliant package licenses that occurred most frequently in the scanned repositories. The returned list also includes the count of repositories in which each non-compliant package license was detected. \nYou can set the `repositories` and `severities` parameters in the request body to filter the results."
operationId: get dashboard data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PackageLicensesRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/PackageLicensesResponse'
description: Non compliant package licenses
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get package licenses
security:
- CustomAuthorizer: []
summary: Top Non-compliant Package Licenses
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/package-licenses\"\n\npayload = {\n \"repositories\": [\"string\"],\n \"size\": 0\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/package-licenses \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"repositories\":[\"string\"],\"size\":0}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/pr-issues-over-time:
post:
description: "Returns the count of the different pull request statuses\n(Failed, Resolved (Failed and was blocking issues were resolved) and Passed) per day for the last 30 days. \nYou can set the `repositories` and `startDate` parameters in the request body to filter the results.<br/>"
operationId: get pr issues over time data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PRIssuesOverTimeRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/PRIssuesOverTimeResponse'
description: Pull Requests Issues Over Time
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get pr issues over time data
security:
- CustomAuthorizer: []
summary: Pull Requests over Time
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/pr-issues-over-time\"\n\npayload = {\n \"repositories\": [\"string\"],\n \"startDate\": \"string\"\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/pr-issues-over-time \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"repositories\":[\"string\"],\"startDate\":\"string\"}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/top-cvss:
post:
description: 'Returns the list of vulnerabilities that have the highest CVSS scores.
The results also include CVE details such as Risk Factors and Severity.
You can set the `repositories` and `severities` parameters in the request body to filter the results.'
operationId: get dashboard top cvss vulnerabilities data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TopCvssVulsRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/TopCvssVulsResponse'
description: Top CVSS Vulnerabilieties
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get top cvss vulnerabilities
security:
- CustomAuthorizer: []
summary: Top CVSS Score Vulnerabilities
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/top-cvss\"\n\npayload = {\n \"repositories\": [\"string\"],\n \"severities\": [\"INFO\"],\n \"size\": 0\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/top-cvss \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"repositories\":[\"string\"],\"severities\":[\"INFO\"],\"size\":0}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/top-vulnerable-repositories:
post:
description: 'Gets the repositories that have the highest number of high-risk errors (High and Critical severity).
You can set the `repositories`, `codeCategories`, and `severities` parameters in the request body to filter the results.'
operationId: get dashboard top vulnerable repositories data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TopVulnerableReposRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/TopVulnerableReposResponse'
description: Top Vulnerable Repositories
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get top vulnerable repositories
security:
- CustomAuthorizer: []
summary: Top Repositories by Critical Error Count
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/top-vulnerable-repositories\"\n\npayload = {\n \"codeCategories\": [\"iac\"],\n \"repositories\": [\"string\"],\n \"severities\": [\"INFO\"],\n \"size\": 0\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/top-vulnerable-repositories \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"codeCategories\":[\"iac\"],\"repositories\":[\"string\"],\"severities\":[\"INFO\"],\"size\":0}'"
servers:
- url: https://api.prismacloud.io
/code/api/v2/dashboard/vcs-scan-issues-over-time:
post:
description: 'Returns the count of day-aggregated issue statuses (Opened Earlier, open today, Fix Pending, Fixed, Suppressed) for the last 30 days.
You can set the `repositories`, `codeCategories`, `severities`, and `startDate` parameters in the request body to filter the results.
Vulnerability data is not included in the response of this endpoint.<br/>
Use the [Top CVSS Score Vulnerabilities](/prisma-cloud/api/code/get-dashboard-top-cvss-vulnerabilities-data) endpoint to retrieve the riskiest vulnerabilities.'
operationId: get vcs scan issues over time data
parameters: []
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/VCSIssuesOverTimeRequest'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/VCSIssuesOverTimeResponse'
description: VCS Scan Issues Over Time
'401':
description: Customer has no permitted accounts
'422':
description: Request arguments validation error
'500':
description: Failed to get vcs scan issues over time
security:
- CustomAuthorizer: []
summary: Code issues over time
tags:
- Dashboard
x-codeSamples:
- lang: Python + Requests
source: "import requests\n\nurl = \"https://api.prismacloud.io/code/api/v2/dashboard/vcs-scan-issues-over-time\"\n\npayload = {\n \"codeCategories\": [\"iac\"],\n \"repositories\": [\"string\"],\n \"severities\": [\"INFO\"],\n \"startDate\": \"string\"\n}\nheaders = {\n \"content-type\": \"application/json\",\n \"authorization\": \"REPLACE_KEY_VALUE\"\n}\n\nresponse = requests.request(\"POST\", url, json=payload, headers=headers)\n\nprint(response.text)"
- lang: Shell + Curl
source: "curl --request POST \\\n --url https://api.prismacloud.io/code/api/v2/dashboard/vcs-scan-issues-over-time \\\n --header 'authorization: REPLACE_KEY_VALUE' \\\n --header 'content-type: application/json' \\\n --data '{\"codeCategories\":[\"iac\"],\"repositories\":[\"string\"],\"severities\":[\"INFO\"],\"startDate\":\"string\"}'"
servers:
- url: https://api.prismacloud.io
/v1/dashboard/scan-statistics:
get:
tags:
- Dashboard
summary: Get scan statistics and risk profile
description: Returns scan counts, target statistics, status breakdown, and risk profile for dashboard display.
operationId: get_scan_statistics_v1_dashboard_scan_statistics_get
responses:
200:
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/ScanStatisticsResponseSchema'
401:
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
security:
- bearerAuth: []
servers:
- url: https://api.sase.paloaltonetworks.com/ai-red-teaming/data-plane
/v1/dashboard/score-trend:
get:
tags:
- Dashboard
summary: Get score trend for a target
description: Returns time-series risk scores grouped by job type for chart display.
operationId: get_score_trend_v1_dashboard_score_trend_get
parameters:
- name: target_id
in: query
required: true
schema:
type: string
format: uuid
description: Target UUID to fetch scores for
title: Target Id
description: Target UUID to fetch scores for
- name: date_range
in: query
required: false
schema:
$ref: '#/components/schemas/DateRangeFilter'
description: Predefined date range filter
default: LAST_7_DAYS
description: Predefined date range filter
- name: start_date
in: query
required: false
schema:
anyOf:
- type: string
format: date
- type: 'null'
description: Custom start date (overrides date_range if both provided)
title: Start Date
description: Custom start date (overrides date_range if both provided)
- name: end_date
in: query
required: false
schema:
anyOf:
- type: string
format: date
- type: 'null'
description: Custom end date (overrides date_range if both provided)
title: End Date
description: Custom end date (overrides date_range if both provided)
responses:
200:
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/ScoreTrendResponseSchema'
422:
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
security:
- bearerAuth: []
servers:
- url: https://api.sase.paloaltonetworks.com/ai-red-teaming/data-plane
/v1/dashboard/overview:
get:
tags:
- Dashboard
summary: Get dashboard overview
description: Returns target counts by type for dashboard display.
operationId: get_overview_v1_dashboard_overview_get
responses:
200:
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/DashboardOverviewResponseSchema'
401:
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
security:
- bearerAuth: []
servers:
- url: https://api.sase.paloaltonetworks.com/ai-red-teaming/mgmt-plane
components:
schemas:
IaCErrorsByCategory:
properties:
category:
description: A category, such as IAM, Logging, Monitoring, Networking, or Kubernetes.
type: string
count:
description: Number of issues for the IaC misconfiguration category.
type: string
required:
- count
- category
type: object
PackageLicenses:
properties:
count:
description: Number of issues for each type of license.
format: double
type: number
license:
description: The package license.
type: string
repos:
description: Number of repositories in which the package with the license issue was detected.
format: double
type: number
required:
- count
- repos
- license
type: object
Size:
description: The maximum number of results included in the response.
format: double
type: number
VCSIssuesOverTimeRequest:
additionalProperties: false
properties:
codeCategories:
description: "- IaC: Filter value to retrieve issues with Infrastructure-as-Code (IaC or iac) templates\n and scripts that provision and manage cloud resources. Prisma Cloud detects issues such\n as misconfigurations and security risks within the code that deploys and manages the infrastructure.\n- Vulnerability: Filter value to retrieve findings related to known security vulnerabilities\n in open-source packages used in applications. These findings highlight potential weaknesses\n that could be exploited by attackers.\n- BuildIntegrity: Filter value to retrieve findings related to the integrity and security\n of the build pipeline or the software supply chain. These findings include checks for\n unauthorized or insecure dependencies, insecure artifact storage, or other issues that\n could compromise the integrity of the software build process.\n- Secrets: Filter value to retrieve findings related to the handling and management of\n sensitive information, such as API keys, passwords, or cryptographic keys, within code\n files. Address these findings to ensure that secrets are properly protected and not exposed\n in the code or configurations.\n- Licenses: Filter value to retrieve issues related to the non-compliance with license requirements.\n Open source packages typically include a license that is either restrictive or permissive.\n Prisma Cloud, by default, identifies and flags instances where open-source software components\n do not include a license, or are carrying an undesired one. Specifically, licenses not approved\n by the Open Source Initiative (OSI) or not recognized by the Software Package Data\n Exchange (SPDX) fall under this undesired category."
items:
$ref: '#/components/schemas/CodeCategoryType'
type: array
repositories:
description: 'The repositories filter enables you to retrieve issues related to one or more repositories.
You must provide the UUIDs of the repositories that you want to include in the filter.
To retrieve the UUID of a repository use the [List repository list](/prisma-cloud/api/code/get-repositories) endpoint.
(the `id` field of the response has the UUID of the repository).'
items:
$ref: '#/components/schemas/Repository'
type: array
severities:
description: "The severity level of the vulnerability or misconfiguration.\n - Critical: Critical severity indicates a high-risk vulnerability or\n misconfiguration that could lead to significant security breaches or\n data leaks. These issues require immediate attention and remediation.\n - High: High severity indicates a significant security issue that has the\n potential to be exploited or result in significant damage if left unaddressed.\n These findings should be addressed as a priority.\n - Medium: Medium severity indicates issues that pose a potential security risk that\n are less severe than Critical and High. Remediation of these issues should be prioritized,\n but they may not require immediate attention.\n - Low: Low severity indicates issues that have a minimal impact on security or are relatively\n low-risk. While they may not pose an immediate threat, it is still recommended to address\n them to maintain a robust security posture.\n - Info: Info severity is used for informational findings or recommendations that\n do not pose an immediate security risk but provide helpful guidance, best practices,\n or suggestions for optimization. These findings can be considered as part of ongoing\n security hygiene efforts."
items:
$ref: '#/components/schemas/Severity'
type: array
startDate:
$ref: '#/components/schemas/StartDate'
required:
- startDate
type: object
VCSIssuesOverTime:
properties:
date:
description: A date in ISO 8601 format. The response includes data for every single day starting from the given `startDate`.
type: string
fixPendingCount:
description: Number of fix pending issues on a given date.
type: string
fixedCount:
description: Number of fixed issues till a given date.
type: string
openCount:
description: Number of open issues on a given date.
type: string
openedTodayCount:
description: Number of open issues added on a given date.
type: string
suppressedCount:
description: Number of suppressed issues on a given date.
type: string
required:
- fixedCount
- fixPendingCount
- suppressedCount
- openedTodayCount
- openCount
- date
type: object
ErrorsBySeverityResponse:
additionalProperties: false
properties:
data:
items:
$ref: '#/components/schemas/ErrorsBySeverity'
type: array
lastScanDate:
description: The time when the last scan was triggered.
type: string
required:
- data
- lastScanDate
type: object
PRIssuesOverTimeResponse:
additionalProperties: false
properties:
data:
items:
$ref: '#/components/schemas/PRIssuesOverTime'
type: array
lastScanDate:
description: The time when the last scan was triggered.
type: string
required:
- data
- lastScanDate
type: object
PRIssuesOverTime:
properties:
date:
description: A date in ISO 8601 format. The response includes data for every single day starting from the given `startDate`.
type: string
failedCount:
description: Number of pull requests that failed till the date.
type: string
failedTodayCount:
description: Number of pull requests that failed on that date.
type: string
passedCount:
description: Number of pull requests that passed till the date.
type: string
resolvedCount:
description: Number of (failed and blocking) pull request issues that were resolved till the date.
type: string
required:
- resolvedCount
- passedCount
- failedTodayCount
- failedCount
- date
type: object
Severity:
description: "The severity level of the vulnerability or misconfiguration.\n - Critical: Critical severity indicates a high-risk vulnerability or\n misconfiguration that could lead to significant security breaches or\n data leaks. These issues require immediate attention and remediation.\n - High: High severity indicates a significant security issue that has the\n potential to be exploited or result in significant damage if left unaddressed.\n These findings should be addressed as a priority.\n - Medium: Medium severity indicates issues that pose a potential security risk that\n are less severe than Critical and High. Remediation of these issues should be prioritized,\n but they may not require immediate attention.\n - Low: Low severity indicates issues that have a minimal impact on security or are relatively\n low-risk. While they may not pose an immediate threat, it is still recommended to address\n them to maintain a robust security posture.\n - Info: Info severity is used for informational findings or recommendations that\n do not pose an immediate security risk but provide helpful guidance, best practices,\n or suggestions for optimization. These findings can be considered as part of ongoing\n security hygiene efforts."
enum:
- INFO
- LOW
- MEDIUM
- HIGH
- CRITICAL
type: string
ErrorsBySeverity:
properties:
count:
description: Number of issues at each severity level.
type: string
severity:
$ref: '#/components/schemas/Severity'
required:
- count
- severity
type: object
TopVulnerableReposResponse:
additionalProperties: false
properties:
data:
items:
$ref: '#/components/schemas/TopVulnerableRepos'
type: array
lastScanDate:
description: The time when the last scan was triggered.
type: string
required:
- data
- lastScanDate
type: object
TopCvssVulsRequest:
additionalProperties: false
properties:
repositories:
description: 'The repositories filter enables you to retrieve issues related to one or more repositories.
You must provide the UUIDs of the repositories that you want to include in the filter.
To retrieve the UUID of a repository use the [List repository list](/prisma-cloud/api/code/get-repositories) endpoint.
(the `id` field of the response has the UUID of the repository).'
items:
$ref: '#/components/schemas/Repository'
type: array
severities:
description: "The severity level of the vulnerability or misconfiguration.\n - Critical: Critical severity indicates a high-risk vulnerability or\n misconfiguration that could lead to significant security breaches or\n data leaks. These issues require immediate attention and remediation.\n - High: High severity indicates a significant security issue that has the\n potential to be exploited or result in significant damage if left unaddressed.\n These findings should be addressed as a priority.\n - Medium: Medium severity indicates issues that pose a potential security risk that\n are less severe than Critical and High. Remediation of these issues should be prioritized,\n but they may not require immediate attention.\n - Low: Low severity indicates issues that have a minimal impact on security or are relatively\n low-risk. While they may not pose an immediate threat, it is still recommended to address\n them to maintain a robust security posture.\n - Info: Info severity is used for informational findings or recommendations that\n do not pose an immediate security risk but provide helpful guidance, best practices,\n or suggestions for optimization. These findings can be considered as part of ongoing\n security hygiene efforts."
items:
$ref: '#/components/schemas/Severity'
type: array
size:
# --- truncated at 32 KB (59 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-dashboard-api-openapi.yml