Palo Alto Networks · JSON Structure

Cortex Xdr Webhooks Incident Payload Structure

The payload delivered to the webhook endpoint for Cortex XDR incident lifecycle events including creation, status changes, and severity changes. Contains incident metadata, alert aggregation counts, assignment information, and data source attribution.

Type: object Properties: 10 Required: 8
Cloud SecurityCybersecurityFirewallNetwork SecuritySASESOARThreat IntelligenceXDR

IncidentPayload is a JSON Structure definition published by Palo Alto Networks, describing 10 properties, of which 8 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

name incident_id creation_time modification_time status severity alert_count assigned_user_mail description alert_sources

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/json-structure/cortex-xdr-webhooks-incident-payload-structure.json",
  "name": "IncidentPayload",
  "description": "The payload delivered to the webhook endpoint for Cortex XDR incident lifecycle events including creation, status changes, and severity changes. Contains incident metadata, alert aggregation counts, assignment information, and data source attribution.\n",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name of the incident, either auto-generated by Cortex XDR from the correlated alert details or manually assigned by an analyst during investigation.\n"
    },
    "incident_id": {
      "type": "string",
      "description": "The unique numeric identifier for the incident, assigned by Cortex XDR upon creation. Used to reference the incident in all subsequent API operations and webhook events.\n"
    },
    "creation_time": {
      "type": "int32",
      "description": "Unix epoch timestamp in milliseconds indicating when the incident was first created by Cortex XDR's correlation engine.\n"
    },
    "modification_time": {
      "type": "int32",
      "description": "Unix epoch timestamp in milliseconds indicating the most recent modification to the incident, including status changes, severity updates, alert additions, and analyst assignments.\n"
    },
    "status": {
      "type": "string",
      "description": "The current investigation status of the incident at the time this webhook notification was dispatched.\n",
      "enum": [
        "new",
        "under_investigation",
        "resolved_threat_handled",
        "resolved_known_issue",
        "resolved_duplicate",
        "resolved_false_positive",
        "resolved_auto"
      ]
    },
    "severity": {
      "type": "string",
      "description": "The current severity level of the incident, determined by the highest-severity correlated alert or manually overridden by an analyst. Drives prioritization in incident queues and escalation workflows.\n",
      "enum": [
        "low",
        "medium",
        "high",
        "critical"
      ]
    },
    "alert_count": {
      "type": "int32",
      "description": "The total number of individual alerts that have been correlated and grouped into this incident at the time of this notification.\n",
      "minimum": 1
    },
    "assigned_user_mail": {
      "type": "string",
      "description": "The email address of the analyst currently assigned to investigate this incident. Empty string when the incident is unassigned.\n"
    },
    "description": {
      "type": "string",
      "description": "A detailed description of the incident providing context about the detected threat activity, affected assets, and attack scope. May be auto-generated from correlated alert content or manually authored by an analyst.\n"
    },
    "alert_sources": {
      "type": "array",
      "description": "List of detection source identifiers that contributed alerts to this incident. Identifies which Cortex XDR engines, modules, or integrated third-party products generated the underlying alerts.\n",
      "items": {
        "type": "string",
        "description": "Name of a detection source that contributed at least one alert to this incident.\n"
      }
    }
  },
  "required": [
    "name",
    "incident_id",
    "creation_time",
    "modification_time",
    "status",
    "severity",
    "alert_count",
    "alert_sources"
  ]
}

Work with this as data

Every JSON Structure 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 json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure in the catalog.
  • 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 JSON Structure
curl "https://apis.io/api/v1/json-structures/cortex-xdr-webhooks-incident-payload-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?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.

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