ActivityWatch Python API Docs | dltHub
Build a ActivityWatch-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
ActivityWatch uses a REST API for communication between aw-server and clients. The API reference documents are available for Python packages like aw_core, aw_client, and aw_server. Most applications should use provided packages instead of accessing the API directly. The REST API base URL is http://localhost:5600/api and Requests may require a Bearer token if the server is configured for token authentication..
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 ActivityWatch data in under 10 minutes.
What data can I load from ActivityWatch?
Here are some of the endpoints you can load from ActivityWatch:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| buckets | /0/buckets/ | GET | List all buckets | |
| bucket_metadata | /0/buckets/{bucket_id} | GET | Get metadata for a specific bucket | |
| bucket_events | /0/buckets/{bucket_id}/events | GET | events | Retrieve events from a bucket |
| server_info | /0/info | GET | Get server information | |
| server_log | /0/log | GET | Retrieve the server log in JSON |
How do I authenticate with the ActivityWatch API?
For a local ActivityWatch instance no authentication is required; if the server is configured with token authentication, include an Authorization: Bearer header.
1. Get your credentials
- Open the ActivityWatch web UI (usually http://localhost:5600). 2. Click the user menu and choose "Settings". 3. Navigate to the "API Tokens" section. 4. Click "Generate new token", give it a name, and copy the displayed token. 5. Store the token securely and use it in the Authorization header as a Bearer token.
2. Add them to .dlt/secrets.toml
[sources.activitywatch_source] token = "your_activitywatch_token_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 ActivityWatch 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 activitywatch_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline activitywatch_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset activitywatch_data The duckdb destination used duckdb:/activitywatch.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline activitywatch_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 buckets and bucket_events from the ActivityWatch 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 activitywatch_source(auth_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:5600/api", "auth": { "type": "bearer", "token": auth_token, }, }, "resources": [ {"name": "buckets", "endpoint": {"path": "0/buckets"}}, {"name": "bucket_events", "endpoint": {"path": "0/buckets/{bucket_id}/events", "data_selector": "events"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="activitywatch_pipeline", destination="duckdb", dataset_name="activitywatch_data", ) load_info = pipeline.run(activitywatch_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("activitywatch_pipeline").dataset() sessions_df = data.buckets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM activitywatch_data.buckets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("activitywatch_pipeline").dataset() data.buckets.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 ActivityWatch 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 ActivityWatch?
Request dlt skills, commands, AGENT.md files, and AI-native context.