DecisionRules Python API Docs | dltHub

DecisionRules is a platform for creating, managing, and executing business rules and decision logic via REST APIs. The REST API base URL is https://api.decisionrules.io and all requests require an Authorization header using Bearer or oauth scheme.

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

---

What data can I load from DecisionRules?

Here are some of the endpoints you can load from DecisionRules:

---

How do I authenticate with the DecisionRules API?

Authentication is performed via the Authorization header using either a Bearer token (with the 'Bearer ' format) or an OAuth access token (with the 'oauth:' format).

1. Get your credentials

To obtain API credentials, sign in to your DecisionRules account and navigate to the 'API Keys' section in the sidebar menu of your space. Click the '+ Add API Key' button to generate a new key; you can then specify the key type (Solver, Management, or Business Intelligence) as required.

2. Add them to .dlt/secrets.toml

Copy
[sources.decisionrules_source]
decisionrules_solver_api_key = "your_solver_api_key_here"
decisionrules_management_api_key = "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:

Copy
uv init
uv add "dlt[hub]"

1. Install the dlt AI harness:

Copy
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:

Copy
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 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:

Copy
uv run python decisionrules_pipeline.py

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

Copy
Pipeline decisionrules_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset decisionrules_data
The duckdb destination used duckdb:/decisionrules.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
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 /rule/solve/{ruleId}/{version} and /rule/{identifier}/{version} from the DecisionRules API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def decisionrules_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.decisionrules.io",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "audit_logs", "endpoint": {"path": "audit/v2/", "data_selector": "audits"}},
            {"name": "rules", "endpoint": {"path": "api/space/items"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="decisionrules_pipeline",
        destination="duckdb",
        dataset_name="decisionrules_data",
    )
    load_info = pipeline.run(decisionrules_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):

Copy
import dlt

data = dlt.pipeline("decisionrules_pipeline").dataset()
sessions_df = data.audit_logs.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM decisionrules_data.audit_logs LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("decisionrules_pipeline").dataset()
data.audit_logs.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:

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.

Copy
uv run dlthub ai toolkit install data-exploration
uv run dlthub ai toolkit install dlthub-platform

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack