Palo Alto Networks · JSON Structure

Cortex Xsiam Data Ingestion Event Data Payload Structure

The payload structure for pre-normalized event data ingestion directly into the XSIAM data lake. Contains all required routing metadata plus the normalized event content for direct dataset indexing.

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

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

Properties

dataset vendor product log_type raw_log timestamp tenant_id event_id

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-xsiam-data-ingestion-event-data-payload-structure.json",
  "name": "EventDataPayload",
  "description": "The payload structure for pre-normalized event data ingestion directly into the XSIAM data lake. Contains all required routing metadata plus the normalized event content for direct dataset indexing.\n",
  "type": "object",
  "properties": {
    "dataset": {
      "type": "string",
      "description": "The target XSIAM dataset name for direct indexing. Must match an existing dataset schema in the XSIAM data lake.\n"
    },
    "vendor": {
      "type": "string",
      "description": "The vendor that produced the source event data.\n"
    },
    "product": {
      "type": "string",
      "description": "The product that generated the source event.\n"
    },
    "log_type": {
      "type": "string",
      "description": "The log type or event category identifier for schema selection during indexing.\n"
    },
    "raw_log": {
      "type": "string",
      "description": "The original raw event content from the source system, preserved alongside normalized fields for audit and reprocessing purposes.\n"
    },
    "timestamp": {
      "type": "datetime",
      "description": "The ISO 8601 date-time string indicating when the original event occurred at the source system.\n"
    },
    "tenant_id": {
      "type": "string",
      "description": "The XSIAM tenant identifier for multi-tenant data routing.\n"
    },
    "event_id": {
      "type": "string",
      "description": "A unique identifier for this event record used for deduplication and correlation reference.\n"
    }
  },
  "required": [
    "dataset",
    "vendor",
    "product",
    "log_type",
    "raw_log",
    "timestamp",
    "tenant_id",
    "event_id"
  ]
}

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-xsiam-data-ingestion-event-data-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.