Palo Alto Networks · Schema
LogDataPayload
The payload structure for raw log data ingestion via the XSIAM HTTP collector. Contains routing metadata to direct the log to the correct parsing pipeline, the raw log content, and optional event identification fields.
Cloud SecurityCybersecurityFirewallNetwork SecuritySASESOARThreat IntelligenceXDR
Properties
| Name | Type | Description |
|---|---|---|
| dataset | string | The target XSIAM dataset name that this log data should be indexed into. Dataset names correspond to XSIAM data lake tables and determine the schema applied during normalization. |
| vendor | string | The name of the vendor that produced the log data. Used in combination with product and log_type to identify the correct parsing rule for normalizing the raw log content. |
| product | string | The name of the specific product or component that generated the log. Used in combination with vendor and log_type to route the log to the appropriate XSIAM parsing pipeline. |
| log_type | string | The log type identifier that classifies the nature of the log content, such as traffic, threat, authentication, or syslog. Used to select the correct normalization schema. |
| raw_log | string | The raw log content in its original format as produced by the source system. May be a syslog message, CSV line, JSON string, CEF record, or any other log format supported by the configured XSIAM parsi |
| timestamp | string | The ISO 8601 date-time string indicating when this log event occurred at the source. If not provided, the ingestion receipt time is used as the event timestamp. |
| tenant_id | string | The XSIAM tenant identifier that this log data belongs to. Used for multi-tenant environments to route data to the correct tenant data lake partition. |
| event_id | string | A unique identifier for this individual log event, generated by the submitting system or the XSIAM ingestion service. Used for deduplication and event correlation tracking. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "LogDataPayload",
"description": "The payload structure for raw log data ingestion via the XSIAM HTTP collector. Contains routing metadata to direct the log to the correct parsing pipeline, the raw log content, and optional event identification fields.\n",
"$id": "https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/json-schema/cortex-xsiam-data-ingestion-log-data-payload-schema.json",
"type": "object",
"properties": {
"dataset": {
"type": "string",
"description": "The target XSIAM dataset name that this log data should be indexed into. Dataset names correspond to XSIAM data lake tables and determine the schema applied during normalization.\n",
"example": "firewall_traffic_raw"
},
"vendor": {
"type": "string",
"description": "The name of the vendor that produced the log data. Used in combination with product and log_type to identify the correct parsing rule for normalizing the raw log content.\n",
"example": "Palo Alto Networks"
},
"product": {
"type": "string",
"description": "The name of the specific product or component that generated the log. Used in combination with vendor and log_type to route the log to the appropriate XSIAM parsing pipeline.\n",
"example": "PAN-OS"
},
"log_type": {
"type": "string",
"description": "The log type identifier that classifies the nature of the log content, such as traffic, threat, authentication, or syslog. Used to select the correct normalization schema.\n",
"example": "traffic"
},
"raw_log": {
"type": "string",
"description": "The raw log content in its original format as produced by the source system. May be a syslog message, CSV line, JSON string, CEF record, or any other log format supported by the configured XSIAM parsing rules.\n",
"example": "Nov 15 10:32:01 PA-3260 1,2024/01/15..."
},
"timestamp": {
"type": "string",
"format": "date-time",
"description": "The ISO 8601 date-time string indicating when this log event occurred at the source. If not provided, the ingestion receipt time is used as the event timestamp.\n",
"example": "2024-01-15T10:32:01.000Z"
},
"tenant_id": {
"type": "string",
"description": "The XSIAM tenant identifier that this log data belongs to. Used for multi-tenant environments to route data to the correct tenant data lake partition.\n",
"example": "xsiam-tenant-001"
},
"event_id": {
"type": "string",
"description": "A unique identifier for this individual log event, generated by the submitting system or the XSIAM ingestion service. Used for deduplication and event correlation tracking.\n",
"example": "evt-20240115-103201-001"
}
},
"required": [
"dataset",
"vendor",
"product",
"log_type",
"raw_log",
"timestamp",
"tenant_id",
"event_id"
]
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema 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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/cortex-xsiam-data-ingestion-log-data-payload"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.