IBM QRadar Python API Docs | dltHub

Build a IBM QRadar-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

IBM QRadar is a security information and event management platform providing a REST API to access, manage, and integrate with security data and configurations. The REST API base URL is https://<console_ip>/api and all requests require either an SEC header for tokens or an Authorization header for basic authentication.

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 IBM QRadar data in under 10 minutes.


What data can I load from IBM QRadar?

Here are some of the endpoints you can load from IBM QRadar:

ResourceEndpointMethodData selectorDescription
help_resources/help/resourcesGETRetrieves a list of resource documentation objects.
help_endpoints/help/endpointsGETRetrieves a list of endpoint documentation objects.
siem_offenses/siem/offensesGETRetrieves a list of offenses.
analytics_rule_groups/analytics/rule_groupsGETRetrieves a list of rule groups.
ariel_databases/ariel/databasesGETRetrieves a list of Ariel databases.

How do I authenticate with the IBM QRadar API?

Requests require an HTTP header for authentication; for authorized service tokens, use the 'SEC' header, and for username/password, use the standard 'Authorization' header with HTTP basic authentication.

1. Get your credentials

  1. Log into your IBM QRadar console. 2. Navigate to the Admin tab. 3. Under System Configuration, click User Management, then select Authorized Services. 4. Click Add Authorized Service. 5. Provide a name for the service, select a Security Profile, and assign a User Role (typically Admin). 6. Set an expiry date or choose 'No Expiry'. 7. Click Create Service. 8. In the Authorized Services Management window, select the newly created service and copy the token string from the Selected Token field. Note: The token is displayed only once; ensure you copy and save it securely before closing the window.

2. Add them to .dlt/secrets.toml

[sources.ibm_qradar_source] qradar_host = "your_qradar_console_ip_or_fqdn" sec_token = "your_authorized_service_token_here"

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 IBM QRadar 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 ibm_qradar_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline ibm_qradar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ibm_qradar_data The duckdb destination used duckdb:/ibm_qradar.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 /ariel/searches and /config/access/authorized_services from the IBM QRadar 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 ibm_qradar_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<console_ip>/api", "auth": {"type": "api_key", "api_key": api_token, "name": "SEC"}, }, "resources": [ {"name": "help_resources", "endpoint": {"path": "help/resources"}}, {"name": "help_endpoints", "endpoint": {"path": "help/endpoints"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ibm_qradar_pipeline", destination="duckdb", dataset_name="ibm_qradar_data", ) load_info = pipeline.run(ibm_qradar_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("ibm_qradar_pipeline").dataset() sessions_df = data.help_resources.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ibm_qradar_data.help_resources LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ibm_qradar_pipeline").dataset() data.help_resources.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 IBM QRadar data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 IBM QRadar?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines