XSOAR Python API Docs | dltHub
Build a XSOAR-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Cortex XSOAR is a security orchestration, automation, and response platform that provides REST APIs for incident management, indicator searching, and system operations. The REST API base URL is https://api-{fqdn} and all requests require x-xdr-auth-id and Authorization headers.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading XSOAR data in under 10 minutes.
What data can I load from XSOAR?
Here are some of the endpoints you can load from XSOAR:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| incidents | /xsoar/public/v1/incidents/search | POST | Search incidents across indices. Supports filtering, paging (page), and limit (size). | |
| lists | /xsoar/public/v1/lists | GET | Get all lists defined in the system. | |
| widgets | /widgets | GET | Get all system widgets. Supports searchAfter for pagination. | |
| indicators | /indicators/search | POST | Search for indicators. Supports pagination and limit. | |
| investigations | /investigations/search | POST | Search for investigations. Supports pagination and limit. |
How do I authenticate with the XSOAR API?
Authentication requires two custom headers: 'x-xdr-auth-id' for the API Key ID and 'Authorization' for the API Key. Standard API keys are sent as raw values, while Advanced keys require signing the request with a timestamp and nonce.
1. Get your credentials
To obtain API credentials in Cortex XSOAR, navigate to 'Settings & Info' > 'Settings' > 'Integrations' > 'API Keys'. Click 'New Key', select the security level (Standard or Advanced), provide a comment if desired, assign a role, and click 'Generate'. You must copy the resulting API key immediately, as it cannot be viewed again. To obtain the API Key ID, locate the 'ID' field in the API Keys table. Finally, click 'Copy API URL' in the same menu to obtain your tenant's FQDN, which is required for all API requests.
2. Add them to .dlt/secrets.toml
[sources.xsoar_source] xsoar_api_key = "your_api_key_here" xsoar_api_key_id = "your_api_key_id_here" xsoar_fqdn = "api-yourfqdn.domain.com"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the XSOAR API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python xsoar_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline xsoar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset xsoar_data The duckdb destination used duckdb:/xsoar.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads incident and indicator (or incidents/search and indicators/search) from the XSOAR API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def xsoar_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api-{fqdn}", "auth": {"type": "api_key", "api_key": api_key, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "lists", "endpoint": {"path": "xsoar/public/v1/lists"}}, {"name": "incidents_search", "endpoint": {"path": "xsoar/public/v1/incidents/search"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="xsoar_pipeline", destination="duckdb", dataset_name="xsoar_data", ) load_info = pipeline.run(xsoar_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("xsoar_pipeline").dataset() sessions_df = data.lists.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM xsoar_data.lists LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("xsoar_pipeline").dataset() data.lists.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load XSOAR data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for XSOAR?
Request dlt skills, commands, AGENT.md files, and AI-native context.