Palo Alto Networks

Palo Alto Networks Notification Profiles API

The Notification Profiles API from Palo Alto Networks — 6 operation(s) for notification profiles.

GitHub OpenAPI

Operations 8

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 /api/cloud/2.0/agg/notifications/profiles List multi-tenant notification profiles · List Notification Profiles #
Ask an LLM
“Which notification profiles are set up for my tenant?”
“What multi-tenant notification profiles do we already have?”
Tell an agent
List all notification profiles for my tenant.
Show every multi-tenant notification profile we have configured.
POST /api/cloud/2.0/agg/notifications/profiles Create a notification profile · Create a Notification Profile #
Ask an LLM
“How do I set up a notification profile that alerts on child tenant upgrades?”
“Is a new notification profile active as soon as I create it?”
Tell an agent
Create notification profile {profileName} for tenants {tenantList} sending {notifTypeDetails} to channels {notifChannels}.
Add profile {profileName} with status {status} and op state {opState} covering tenants {tenantList}, types {notifTypeDetails}, channels {notifChannels}.
GET /api/cloud/2.0/agg/notifications/profiles/{notification-profile-id} Get a notification profile · Get a Tenant's Notification Profile #
Ask an LLM
“What tenants and channels does one notification profile cover?”
“Can I look up a single notification profile by its ID?”
Tell an agent
Get notification profile {notification-profile-id}.
Show the inputs and output channels of notification profile {notification-profile-id}.
DELETE /api/cloud/2.0/agg/notifications/profiles/{notification-profile-id} Delete a notification profile · Delete a Notification Profile #
Ask an LLM
“How do I permanently remove a notification profile?”
“Can I delete a multi-tenant notification profile we no longer need?”
Tell an agent destructive · confirm first
Delete notification profile {notification-profile-id}.
Remove the unused notification profile {notification-profile-id} for good.
PUT /api/cloud/2.0/agg/notifications/profiles/opstate Enable or disable a notification profile · Enable / Disable Profile #
Ask an LLM
“How do I turn on a notification profile so it starts sending alerts?”
“Can I pause a notification profile without deleting it?”
Tell an agent
Set notification profile {profileId} to op state {opState}.
Enable notification profile {profileId}.
GET /api/cloud/2.0/agg/notifications/profiles/types List notification types and categories · Retrieve Notification Types #
Ask an LLM
“What notification types and categories can a profile subscribe to?”
“Which sub-categories exist under each notification category?”
Tell an agent
List the valid notification types, categories and sub-categories.
Show me which notification categories I can pick for a profile.
POST /api/cloud/2.0/agg/notifications/profiles/webhook/test Test a notification webhook · Webhook Connectivity Check #
Ask an LLM
“Can the notification service reach my webhook URL before I use it in a profile?”
“How do I verify a webhook's auth token works for notifications?”
Tell an agent
Test webhook connectivity to {urls} using {authType} auth with token {token}.
Check that the notification service can reach webhook {urls} with {authType} token {token}.
POST /api/cloud/2.0/agg/notifications/profiles/retryOp Retry pushing an incident profile to tenants · Incident Profile Retry Operation #
Ask an LLM
“What can I do when an incident profile failed to push to some child tenants?”
“Can I retry an incident profile push for just a few tenants?”
Tell an agent
Retry pushing incident profile {profileId} to child tenants {tenantList}.
Re-push incident profile {profileId} to the tenants where it failed.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-notification-profiles-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-notification-profiles-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-notification-profiles-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Multi-Tenant Notifications Notification Profiles API
  version: '1.0'
security:
- bearerAuth: []
tags:


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