Load Kantata data to DuckDB

Kantata (formerly Mavenlink) is a project and resource management platform providing a RESTful API for accessing workspaces, projects, tasks, users, and time tracking resources. Everything needed to build a working Kantata → 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 Kantata 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 Kantata 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 Kantata 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.

---

Kantata API at a glance

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

---

How do I authenticate with the Kantata API?

All requests to the Kantata API require an Authorization header with the value set to 'Bearer '.

1. Get your credentials

To obtain credentials, you must be an Account Administrator. Follow these steps in the Kantata OX dashboard: 1. Navigate to Settings, then select API in the left navigation menu. 2. Select View your Account's Registered Applications. 3. Click Register a new Kantata OX Application. 4. Provide an Application Name and Application Callback URI, then save. 5. Once registered, view the application details and click Show your OAuth Token to retrieve your OAuth bearer token.

2. Add them to .dlt/secrets.toml

Copy
[sources.kantata_source]
api_key = "your_oauth_bearer_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 Kantata data can I load into DuckDB?

These are the Kantata endpoints dlt can load into DuckDB:

---

How do I load only new Kantata records?

Kantata exposes updated_after on workspaces, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "workspaces", "endpoint": {
    "path": "workspaces",
    "data_selector": "workspaces",
    "incremental": {"cursor_path": "updated_after", "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 Kantata pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading workspaces and account_memberships from the Kantata API into DuckDB:

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

@dlt.source
def kantata_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.mavenlink.com/api/v1/",
            "auth": {"type": "bearer", "token": token},
        },
        "resources": [
            {"name": "workspaces", "endpoint": {"path": "workspaces", "data_selector": "workspaces"}},
            {"name": "workspace_resources", "endpoint": {"path": "workspace_resources", "data_selector": "workspace_resources"}}
        ],
    }
    yield from rest_api_resources(config)


def load_kantata_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="kantata_pipeline",
        destination="duckdb",
        dataset_name="kantata_data",
    )
    load_info = pipeline.run(kantata_source())
    print(load_info)


if __name__ == "__main__":
    load_kantata_to_duckdb()

Run it with python kantata_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 Kantata 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("kantata_pipeline").dataset()
df = data.workspaces.df()
print(df.head())

SQL:

Copy
SELECT * FROM kantata_data.workspaces LIMIT 10;

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

---

How do I deploy the Kantata 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 Kantata 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 Kantata 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