Load Stellar Cyber data in Python using dltHub
Build a Stellar Cyber-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Stellar Cyber is an Open XDR platform that provides a REST API for automating security operations including alert handling, tenant administration, and system management. The REST API base URL is https://{platform_hostname}/connect/api/v1 and all requests require a Bearer token (JWT) in the Authorization header.
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 Stellar Cyber data in under 10 minutes.
What data can I load from Stellar Cyber?
Here are some of the endpoints you can load from Stellar Cyber:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| cases | /cases | GET | data | Retrieve a list of security cases |
| incidents | /incidents | GET | Retrieve a list of security incidents | |
| tenants | /tenants | GET | List tenants | |
| alert_watchers | /alert_watchers | GET | List alert watchers | |
| queries | /queries | GET | List platform queries |
How do I authenticate with the Stellar Cyber API?
Authentication uses a JWT obtained from the /connect/api/v1/access_token endpoint. The token must be sent in the Authorization header as a Bearer token, e.g., 'Authorization: Bearer '.
1. Get your credentials
To obtain an API key for the Stellar Cyber REST API, follow these steps in the Stellar Cyber dashboard: 1. Navigate to 'System' > 'ORGANIZATION MANAGEMENT' > 'Users'. 2. Locate the relevant user account and click the 'Edit' icon. 3. In the user dialog box, select the 'API Keys' tab. 4. Click 'Create API Key', enter a name for the key, and click 'Create'. 5. Copy the generated key immediately and save it securely, as it will not be retrievable later. Note that scoped API keys are limited by the user's RBAC privileges and tenancy. Super Admins with root scope can also generate all-access tokens via the 'API Access' section if required.
2. Add them to .dlt/secrets.toml
[sources.stellar_cyber_source] api_key = "REPLACE_ME"
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 Stellar Cyber 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 stellar_cyber_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline stellar_cyber_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset stellar_cyber_data The duckdb destination used duckdb:/stellar_cyber.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 /connect/api/v1/access_token and /api/v1/ (base path) from the Stellar Cyber 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 stellar_cyber_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{platform_hostname}/connect/api/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "cases", "endpoint": {"path": "cases", "data_selector": "data"}}, {"name": "incidents", "endpoint": {"path": "incidents", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="stellar_cyber_pipeline", destination="duckdb", dataset_name="stellar_cyber_data", ) load_info = pipeline.run(stellar_cyber_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("stellar_cyber_pipeline").dataset() sessions_df = data.cases.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM stellar_cyber_data.cases LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("stellar_cyber_pipeline").dataset() data.cases.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 Stellar Cyber 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 Stellar Cyber?
Request dlt skills, commands, AGENT.md files, and AI-native context.