DecisionRules Python API Docs | dltHub
Build a DecisionRules-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The DecisionRules Management API allows creation and management of business rules via RESTful endpoints. It supports versioning and rule publishing. The API uses JSON for request and response formats. The REST API base URL is https://api.decisionrules.io/api and all requests require a Bearer token (Management API Key) 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 pip install "dlt[workspace]" and start loading DecisionRules data in under 10 minutes.
What data can I load from DecisionRules?
Here are some of the endpoints you can load from DecisionRules:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| space_items | /space/items | GET | (top-level array) | Lists all rules/items in the space (returns JSON array) |
| tags_items | /tags/items | GET | (top-level array) | Lists rules filtered by tags (returns JSON array) |
| folder_node | /folder/{nodeId} | GET | children | Returns folder tree object with 'children' array of folders/rules |
| folder_export | /folder/export/{nodeId} | GET | export.data.rules | Exports folder with rules; response contains nested 'export' object with 'data' and 'rules' |
| rule_get | /rule/{identifier}/{version} | GET | (top-level object) | Returns full rule object (single object response) |
| tools_dependencies | /tools/dependencies/{identifier}/{version} | GET | dependencies | Returns object with 'dependencies' array and 'rule' object |
| rule_flow_export | /api/rule-flow/export/{ruleFlowId}/{version} | GET | (object) | Exports rule flow; returns object (may contain nested structures) |
| folder_find | /folder/find | POST | (object) | Finds/fetches folder info (response example: object) |
| folders_export_all | /folder/export/{nodeId} | GET | export.data.structure | Exports folder content (duplicate listing for clarity) |
| rule_get_by_alias | /rule/{identifier}/{version}?path=... | GET | (object) | GET rule supporting path or identifier targeting |
How do I authenticate with the DecisionRules API?
Provide 'Authorization: Bearer <MANAGEMENT_API_KEY>' on every request. Use the Management API Key (bearer token) associated with your DecisionRules space/region.
1. Get your credentials
- Log in to your DecisionRules account (app or admin portal).
- Navigate to the Management API / API Keys or Integrations section in account settings.
- Create or copy an existing 'Management API Key' (bearer token) scoped to the target Space/region.
- Use that token as 'Bearer ' in the Authorization header.
2. Add them to .dlt/secrets.toml
[sources.decisionrules_management_api_source] management_token = "your_management_api_key_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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 DecisionRules 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:
python decisionrules_management_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline decisionrules_management_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset decisionrules_management_api_data The duckdb destination used duckdb:/decisionrules_management_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline decisionrules_management_api_pipeline 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 space_items and rule_get from the DecisionRules 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 decisionrules_management_api_source(management_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.decisionrules.io/api", "auth": { "type": "bearer", "token": management_token, }, }, "resources": [ {"name": "space_items", "endpoint": {"path": "space/items"}}, {"name": "rule_get", "endpoint": {"path": "rule/{identifier}/{version}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="decisionrules_management_api_pipeline", destination="duckdb", dataset_name="decisionrules_management_api_data", ) load_info = pipeline.run(decisionrules_management_api_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("decisionrules_management_api_pipeline").dataset() sessions_df = data.space_items.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM decisionrules_management_api_data.space_items LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("decisionrules_management_api_pipeline").dataset() data.space_items.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 DecisionRules 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 Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for DecisionRules?
Request dlt skills, commands, AGENT.md files, and AI-native context.