Load Kanboard data to DuckDB

Kanboard is a project management software that provides a JSON-RPC based API for managing tasks, projects, and users. Everything needed to build a working Kanboard → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Kanboard to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Kanboard to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Kanboard API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Kanboard API at a glance

These values come from the Kanboard API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Kanboard API?

The API uses HTTP Basic Authentication, where the username is 'jsonrpc' and the password is the API token, or standard user credentials. Alternatively, a custom HTTP header can be configured in config.php to send base64-encoded 'username:password' credentials.

1. Get your credentials

To obtain Kanboard API credentials, log in to your Kanboard instance as an administrator or regular user. For application-level access (which does not check user-specific permissions), navigate to 'Settings' > 'API' and copy the generated API token. For user-level access (which enforces specific user and project permissions), use your account password or generate a personal access token if available in your profile settings. When authenticating, use the username 'jsonrpc' alongside the application-level API token as the password.

2. Add them to .dlt/secrets.toml

Copy
[sources.kanboard_source]
api_username = "jsonrpc"
api_password = "your_api_token_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Kanboard data can I load into DuckDB?

These are the Kanboard endpoints dlt can load into DuckDB:

---

How do I load only new Kanboard records?

The Kanboard API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "projects", "endpoint": {
    "path": "jsonrpc.php",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Kanboard pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading Kanboard utilizes a single, unified JSON-RPC endpoint for all interactions, commonly referred to as /jsonrpc.php. As there is only one functional endpoint for the API, jsonrpc.php is the primary interface used for all method calls (such as those for tasks and projects). from the Kanboard API into DuckDB:

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

@dlt.source
def kanboard_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://YOUR_SERVER/jsonrpc.php",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key},
        },
        "resources": [
            {"name": "projects", "endpoint": {"path": "jsonrpc.php", "data_selector": "result"}},
            {"name": "tasks", "endpoint": {"path": "jsonrpc.php", "data_selector": "result"}}
        ],
    }
    yield from rest_api_resources(config)


def load_kanboard_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="kanboard_pipeline",
        destination="duckdb",
        dataset_name="kanboard_data",
    )
    load_info = pipeline.run(kanboard_source())
    print(load_info)


if __name__ == "__main__":
    load_kanboard_to_duckdb()

Run it with python kanboard_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Kanboard data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("kanboard_pipeline").dataset()
df = data.projects.df()
print(df.head())

SQL:

Copy
SELECT * FROM kanboard_data.projects LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Kanboard to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Kanboard loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Kanboard data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack