Palo Alto Networks · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Palo Alto Networks Widgets API

6 actions 6 updates phrasing extends openapi/palo-alto-networks-widgets-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Palo Alto Networks's API. It is a proposal applied on top of the contract, not a document Palo Alto Networks publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 6

$.info
$.paths['/commandcenter/api/v1/metrics/alert-count-by-resolution-reason'].post
$.paths['/commandcenter/api/v1/metrics/alert-mean-resolution-time'].post
$.paths['/adoptionadvisor/api/v2/compute/vulnerabilities/trend'].post
$.paths['/adoptionadvisor/api/v2/cspm/riskyasset/trend'].post
$.paths['/adoptionadvisor/api/v2/compute/discovered-secured/trend'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Palo Alto Networks Widgets API
  version: 1.0.0
extends: openapi/palo-alto-networks-widgets-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 5
- target: $.paths['/commandcenter/api/v1/metrics/alert-count-by-resolution-reason'].post
  update:
    x-apievangelist-phrasing:
      intent: Count resolved alerts by resolution reason
      effect: read
      questions:
      - Why are my alerts being resolved, broken down by reason?
      - How many alerts were resolved for each resolution reason in a time range?
      instructions:
      - text: Count resolved alerts by resolution reason over {timeRange}.
        slots:
          timeRange: requestBody.timeRange
      - text: Break down resolved alerts by reason for {timeRange} with filters {filters}.
        slots:
          timeRange: requestBody.timeRange
          filters: requestBody.filters
      method: generated
      generated: '2026-09-26'
- target: $.paths['/commandcenter/api/v1/metrics/alert-mean-resolution-time'].post
  update:
    x-apievangelist-phrasing:
      intent: Get mean alert resolution time by severity
      effect: read
      questions:
      - How long does it take on average to resolve alerts of each severity?
      - What's our mean time to resolve alerts over a period?
      instructions:
      - text: Get the mean alert resolution time per severity for {timeRange}.
        slots:
          timeRange: requestBody.timeRange
      - text: Show average days to resolve alerts over {timeRange} using filters {filters}.
        slots:
          timeRange: requestBody.timeRange
          filters: requestBody.filters
      method: generated
      generated: '2026-09-26'
- target: $.paths['/adoptionadvisor/api/v2/compute/vulnerabilities/trend'].post
  update:
    x-apievangelist-phrasing:
      intent: Get the vulnerabilities trend over time
      effect: read
      questions:
      - Are we discovering more vulnerabilities than we resolve over time?
      - What does the vulnerability trend look like across images, hosts, functions and containers?
      instructions:
      - text: Get the vulnerabilities trend for {timeRange}.
        slots:
          timeRange: requestBody.timeRange
      - text: Show vulnerabilities discovered versus resolved over time.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/adoptionadvisor/api/v2/cspm/riskyasset/trend'].post
  update:
    x-apievangelist-phrasing:
      intent: Get the trend of assets generating alerts
      effect: read
      questions:
      - Which cloud assets are generating alerts?
      - How has the number of risky assets with alerts changed over time?
      instructions:
      - text: Get the assets generating alerts over {timeRange}.
        slots:
          timeRange: requestBody.timeRange
      - text: List risky assets with alerts matching {filters}.
        slots:
          filters: requestBody.filters
      method: generated
      generated: '2026-09-26'
- target: $.paths['/adoptionadvisor/api/v2/compute/discovered-secured/trend'].post
  update:
    x-apievangelist-phrasing:
      intent: Compare discovered versus secured resources
      effect: read
      questions:
      - How many discovered resources are actually protected by defenders?
      - What's the gap between resources found by Cloud Discovery and those secured?
      instructions:
      - text: Get discovered versus secured resources for {timeRange}.
        slots:
          timeRange: requestBody.timeRange
      - text: Show how many discovered resources are secured by defenders.
      method: generated
      generated: '2026-09-26'