ActivityWatch Python API Docs | dltHub

Build a ActivityWatch-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

ActivityWatch is a privacy-focused open-source automated time tracker that uses a REST API for communication between the server and clients. The REST API base URL is http://localhost:5600/api and all requests require a Bearer token if token authentication is enabled in server settings.

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


What data can I load from ActivityWatch?

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

ResourceEndpointMethodData selectorDescription
info/api/0/infoGETGet server information
buckets/api/0/buckets/GETList available buckets
bucket_metadata/api/0/buckets/<bucket_id>GETGet specific bucket metadata
events/api/0/buckets/<bucket_id>/eventsGETGet events from a bucket
event_count/api/0/buckets/<bucket_id>/events/countGETGet event count for a bucket

How do I authenticate with the ActivityWatch API?

When the server is configured with token authentication, requests must include an 'Authorization' header with the value 'Bearer '. Authentication is optional and opt-in by the user in the server configuration.

1. Get your credentials

  1. Locate your ActivityWatch configuration file, typically named config.toml. On Linux, this is often found in ~/.config/activitywatch/aw-server/config.toml (or similar XDG-compliant paths). On other platforms, check the ActivityWatch data directory.\n2. Open the file in a text editor.\n3. Add an [auth] section if it does not already exist.\n4. Define an api_key field under the [auth] section with your desired secure string (e.g., 'api_key = "your-secret-key-here"').\n5. Save the file and restart the ActivityWatch server to apply the changes. This key will now be required for all authenticated requests via the Authorization: Bearer <api_key> header.

2. Add them to .dlt/secrets.toml

[sources.activitywatch_source] auth_token = "REPLACE_ME"

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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

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:

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

uv run 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:

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 /api/0/info and /api/0/buckets 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": "api/0/buckets/"}}, {"name": "events", "endpoint": {"path": "api/0/buckets/{bucket_id}/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:

DestinationExample 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 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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for ActivityWatch?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines