Palo Alto Networks

Palo Alto Networks Compliance Posture API

The Compliance Posture API methods provide information related to your compliance posture across various compliance standards. The filters available through the API enable you to view your status across different cloud accounts, regions, and for specific compliance mandates.

GitHub OpenAPI

Operations 26

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

GET /compliance/posture Get the v1 compliance pass/fail breakdown · Get Compliance Statistics Breakdown - GET #
Ask an LLM
“How do I get passed and failed counts across all my compliance standards for the last few days using the original v1 posture endpoint?”
“Can the legacy compliance statistics GET call be narrowed to one cloud account or region with a relative time window?”
Tell an agent
Using the v1 GET compliance posture call, show pass/fail stats for all standards over the last {timeAmount} {timeUnit} ({timeType} time).
Pull the v1 compliance breakdown for cloud account {account}, {timeType} time, last {timeAmount} {timeUnit}.
POST /compliance/posture Query the v1 compliance breakdown with body filters · Get Compliance Statistics Breakdown - POST #
Ask an LLM
“Is there a POST version of the old compliance statistics breakdown that takes filters and a time range in the request body?”
“Can I choose which fields come back when I request the v1 all-standards compliance breakdown by POST?”
Tell an agent
POST to the v1 compliance posture endpoint with filters {filters} and time range {timeRange} to get the all-standards breakdown.
Request only fields {fields} from the v1 all-standards compliance breakdown via POST.
GET /compliance/posture/{complianceId} Get v1 compliance stats for one standard · Get Compliance Statistics for Standard ID - GET #
Ask an LLM
“What are the passed and failed results for a single compliance standard over a set time window in the v1 API?”
“Can I break down one standard's compliance by requirement for a specific cloud type using the older GET endpoint?”
Tell an agent
Get v1 pass/fail statistics for compliance standard {complianceId} over the last {timeAmount} {timeUnit} ({timeType}).
Show v1 compliance stats for standard {complianceId} on cloud type {cloudType}, {timeType} time, {timeAmount} {timeUnit}.
POST /compliance/posture/{complianceId} Query v1 compliance stats for a standard by POST · Get Compliance Statistics for Standard ID - POST #
Ask an LLM
“Can I send body filters and a time range when fetching one standard's compliance statistics in the legacy API?”
“Which POST call returns the v1 pass/fail breakdown for a single compliance standard ID?”
Tell an agent
POST a v1 statistics request for compliance standard {complianceId} with time range {timeRange}.
Fetch the v1 breakdown for standard {complianceId} filtered by {filters} using the POST form.
GET /compliance/posture/{complianceId}/{requirementId} Get v1 compliance stats for one requirement · Get Compliance Statistics for Requirement ID - GET #
Ask an LLM
“How can I see section-level pass/fail results for one requirement inside a compliance standard with the v1 API?”
“Can the legacy requirement statistics GET be limited to a single compliance section?”
Tell an agent
Get v1 section stats for requirement {requirementId} of standard {complianceId}, {timeType} time, last {timeAmount} {timeUnit}.
Show v1 results for section {section} in requirement {requirementId} of standard {complianceId} over {timeAmount} {timeUnit} ({timeType}).
POST /compliance/posture/{complianceId}/{requirementId} Query v1 requirement compliance stats by POST · Get Compliance Statistics for Requirement ID - POST #
Ask an LLM
“Is there a POST endpoint for the old per-requirement compliance breakdown that accepts body filters?”
“Can I sort or page the v1 section results for one compliance requirement?”
Tell an agent
POST a v1 stats request for requirement {requirementId} in standard {complianceId} with time range {timeRange}.
Get the v1 per-requirement breakdown for {requirementId} under {complianceId}, sorted by {sortBy}, via POST.
GET /compliance/posture/trend Get the v1 compliance trend over time · Get Compliance Trend - GET #
Ask an LLM
“How has my overall pass/fail compliance trended over the past month in the v1 API?”
“Can I see the legacy compliance trend for just one cloud region?”
Tell an agent
Show the v1 compliance trend across all standards for the last {timeAmount} {timeUnit} ({timeType}).
Get the v1 compliance trend in region {region}, {timeType} time, {timeAmount} {timeUnit}.
POST /compliance/posture/trend Query the v1 compliance trend by POST · Get Compliance Trend - POST #
Ask an LLM
“Can I request the old overall compliance trend with filters and a time range in a POST body?”
“Which legacy POST call returns the pass/fail trend summary for all standards?”
Tell an agent
POST a v1 overall compliance trend request covering time range {timeRange}.
Get the v1 all-standards compliance trend filtered by {filters} using POST.
GET /compliance/posture/trend/{complianceId} Get the v1 compliance trend for one standard · Get Compliance Trend for Standard ID - GET #
Ask an LLM
“Is my score on one compliance standard improving over time according to the v1 trend endpoint?”
“Can I view the legacy trend for a single standard restricted to one cloud account?”
Tell an agent
Show the v1 compliance trend for standard {complianceId} over the last {timeAmount} {timeUnit} ({timeType}).
Get the v1 trend for standard {complianceId} in account {account}, {timeType} time, {timeAmount} {timeUnit}.
POST /compliance/posture/trend/{complianceId} Query the v1 trend for a standard by POST · Get Compliance Trend for Standard ID - POST #
Ask an LLM
“Can I pass a time range in the body when pulling one standard's trend from the older API?”
“Which POST endpoint gives the v1 pass/fail trend for a given compliance standard ID?”
Tell an agent
POST a v1 trend request for standard {complianceId} with time range {timeRange}.
Get the v1 trend for standard {complianceId} with body filters {filters}.
GET /compliance/posture/trend/{complianceId}/{requirementId} Get the v1 compliance trend for a requirement · Get Compliance Trend for Requirement ID - GET #
Ask an LLM
“How has a single compliance requirement's pass/fail trend moved over the last few weeks in the v1 API?”
“Can the legacy requirement trend be filtered to one section ID?”
Tell an agent
Show the v1 trend for requirement {requirementId} in standard {complianceId} for the last {timeAmount} {timeUnit} ({timeType}).
Get the v1 requirement trend for {requirementId} under {complianceId}, section {section}, {timeType} {timeAmount} {timeUnit}.
POST /compliance/posture/trend/{complianceId}/{requirementId} Query the v1 requirement trend by POST · Get Compliance Trend for Requirement ID - POST #
Ask an LLM
“Is there a legacy POST call for the trend of one requirement that takes a body time range?”
“Can I filter the v1 per-requirement trend with body filters instead of query parameters?”
Tell an agent
POST a v1 trend request for requirement {requirementId} of standard {complianceId} over {timeRange}.
Get the v1 requirement trend for {requirementId} in {complianceId} filtered by {filters} via POST.
GET /filter/compliance/posture/suggest List compliance overview filters and options · Get Compliance Overview Filters and Options #
Ask an LLM
“What filters can I apply to compliance posture data, and what saved options exist for each?”
“Which filter keys does the compliance overview support?”
Tell an agent
List all compliance posture filter keys with their available and saved options.
Show me the filters supported on the compliance overview.
POST /filter/compliance/posture/suggest Autocomplete values for a compliance filter · List Compliance Overview Filter Autocomplete Suggestions #
Ask an LLM
“What values can I pick for a specific compliance posture filter?”
“Can I fuzzy-search the options of one compliance overview filter by typing part of a value?”
Tell an agent
Suggest values for compliance filter {filterName}.
Autocomplete compliance filter {filterName} for options containing {query}.
GET /v2/compliance/posture Get the V2 compliance breakdown for all standards · Get Compliance Statistics Breakdown V2 - GET #
Ask an LLM
“How do I get a current pass/fail summary across every compliance standard with the V2 API?”
“Can I filter the V2 all-standards compliance breakdown by cloud type or account?”
Tell an agent
Get the V2 compliance statistics breakdown across all standards.
Show the V2 all-standards compliance breakdown for cloud account {account}.
POST /v2/compliance/posture Query the V2 all-standards breakdown by POST · Get Compliance Statistics Breakdown V2 - POST #
Ask an LLM
“Can I use body filters and pick fields when requesting the V2 compliance breakdown across all standards?”
“Which V2 POST call summarizes pass/fail results for every compliance standard?”
Tell an agent
POST a V2 all-standards compliance breakdown request with filters {filters}.
Return only fields {fields} in the V2 all-standards compliance breakdown.
GET /v2/compliance/posture/{complianceId} Get V2 compliance stats for one standard · Get Compliance Statistics for Standard ID V2 - GET #
Ask an LLM
“How is one compliance standard doing right now according to the V2 statistics endpoint?”
“Can I scope the V2 standard breakdown to a single requirement name?”
Tell an agent
Get the V2 pass/fail breakdown for compliance standard {complianceId}.
Show V2 stats for standard {complianceId} limited to requirement {requirement}.
POST /v2/compliance/posture/{complianceId} Query V2 stats for a standard by POST · Get Compliance Statistics for Standard ID V2 - POST #
Ask an LLM
“Can I request specific fields when POSTing for one standard's V2 compliance statistics?”
“Which V2 POST call returns the breakdown for a given compliance standard ID with body filters?”
Tell an agent
POST a V2 statistics request for standard {complianceId} with filters {filters}.
Get V2 stats for standard {complianceId} returning only {fields}.
GET /v2/compliance/posture/{complianceId}/{requirementId} Get V2 compliance stats for one requirement · Get Compliance Statistics for Requirement ID V2 - GET #
Ask an LLM
“What are the section-level pass/fail results for a single requirement in the V2 API?”
“Can I narrow the V2 requirement breakdown to one cloud region?”
Tell an agent
Get V2 section stats for requirement {requirementId} of standard {complianceId}.
Show V2 results for requirement {requirementId} in {complianceId} for region {region}.
POST /v2/compliance/posture/{complianceId}/{requirementId} Query V2 requirement stats by POST · Get Compliance Statistics for Requirement ID V2 - POST #
Ask an LLM
“Is there a V2 POST endpoint for one requirement's section breakdown that accepts filters in the body?”
“Can I page through the V2 per-requirement compliance results?”
Tell an agent
POST a V2 stats request for requirement {requirementId} in standard {complianceId} with filters {filters}.
Get the next {limit} V2 section results for requirement {requirementId} of {complianceId}.
GET /v2/compliance/posture/trend Get the V2 compliance trend for all standards · Get Compliance Trend V2 - GET #
Ask an LLM
“Is my overall compliance getting better or worse over time according to the V2 trend?”
“Can I see the V2 compliance trend for just one cloud type?”
Tell an agent
Show the V2 overall compliance pass/fail trend.
Get the V2 compliance trend for cloud type {cloudType}.
POST /v2/compliance/posture/trend Query the V2 overall trend by POST · Get Compliance Trend V2 - POST #
Ask an LLM
“Can I send a time range and filters in the body to get the V2 all-standards compliance trend?”
“Which V2 POST call returns the trend summary across every standard?”
Tell an agent
POST a V2 all-standards trend request over time range {timeRange}.
Get the V2 overall compliance trend filtered by {filters} using POST.
GET /v2/compliance/posture/trend/{complianceId} Get the V2 trend for one standard · Get Compliance Trend for Standard ID V2 - GET #
Ask an LLM
“How has a particular compliance standard trended in the V2 API?”
“Can I filter one standard's V2 trend to a single cloud account?”
Tell an agent
Show the V2 pass/fail trend for standard {complianceId}.
Get the V2 trend for standard {complianceId} in cloud account {account}.
POST /v2/compliance/posture/trend/{complianceId} Query the V2 standard trend by POST · Get Compliance Trend for Standard ID V2 - POST #
Ask an LLM
“Is there a V2 POST version of the per-standard compliance trend that takes body filters?”
“Can I choose the returned fields for one standard's V2 trend?”
Tell an agent
POST a V2 trend request for standard {complianceId} with filters {filters}.
Get the V2 trend for standard {complianceId} returning fields {fields}.
GET /v2/compliance/posture/trend/{complianceId}/{requirementId} Get the V2 trend for one requirement · Get Compliance Trend for Requirement ID V2 - GET #
Ask an LLM
“How has one compliance requirement trended over time in the V2 API?”
“Can the V2 requirement trend be filtered to a single section?”
Tell an agent
Show the V2 trend for requirement {requirementId} in standard {complianceId}.
Get the V2 trend of section {section} under requirement {requirementId} of {complianceId}.
POST /v2/compliance/posture/trend/{complianceId}/{requirementId} Query the V2 requirement trend by POST · Get Compliance Trend for Requirement ID V2 - POST #
Ask an LLM
“Is there a V2 POST call for one requirement's trend that accepts filters in the body?”
“Can I sort the V2 per-requirement trend results?”
Tell an agent
POST a V2 trend request for requirement {requirementId} of standard {complianceId} filtered by {filters}.
Get the V2 requirement trend for {requirementId} in {complianceId} sorted by {sortBy}.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-compliance-posture-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-compliance-posture-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-compliance-posture-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Palo Alto Networks Compliance Posture API
  version: Latest
  contact: {}
  description: 'Operations tagged Compliance Posture across 2 of this provider''s published API definitions: palo-alto-cspm-complianceposture-openapi.json, palo-alto-cspm-consolidated-spec-cspm-spec-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.prismacloud.io
- url: https://api2.prismacloud.io
- url: https://api3.prismacloud.io
- url: https://api4.prismacloud.io
- url: https://api.anz.prismacloud.io
- url: https://api.eu.prismacloud.io
- url: https://api2.eu.prismacloud.io
- url: https://api.gov.prismacloud.io
- url: https://api.prismacloud.cn
- url: https://api.ca.prismacloud.io
- url: https://api.sg.prismacloud.io
- url: https://api.uk.prismacloud.io
- url: https://api.ind.prismacloud.io
- url: https://api.jp.prismacloud.io
- url: https://api.fr.prismacloud.io
tags:


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