Clockodo Python API Docs | dltHub

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

Last updated:

Clockodo is a cloud-based time-tracking and project management application that provides a REST API for automating time entries and project data management. The REST API base URL is https://my.clockodo.com/api and requests require X-ClockodoApiUser and X-ClockodoApiKey headers along with an application identification header.

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


What data can I load from Clockodo?

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

ResourceEndpointMethodData selectorDescription
entriesv2/entriesGETentriesList time entries
usersv2/usersGETusersList co-workers
customersv2/customersGETcustomersList customers
projectsv2/projectsGETprojectsList projects
servicesv2/servicesGETservicesList services

How do I authenticate with the Clockodo API?

Authentication requires the X-ClockodoApiUser header (user email) and the X-ClockodoApiKey header (API key). Additionally, every request must include the X-Clockodo-External-Application header, formatted as 'name of application;email address', to identify the integrating application.

1. Get your credentials

Log in to your Clockodo account via the web interface. Navigate to your personal settings (often found under 'Personal data' or via the user menu). Locate the 'API' or 'Personal data' section to find or generate your unique API key. Your account email address is used alongside this API key for authentication.

2. Add them to .dlt/secrets.toml

[sources.clockodo_source] api_key = "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 Clockodo 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 clockodo_pipeline.py

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

Pipeline clockodo_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset clockodo_data The duckdb destination used duckdb:/clockodo.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/v2/entries and /api/v2/users from the Clockodo 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 clockodo_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://my.clockodo.com/api", "auth": {"type": "api_key", "api_key": api_key, "name": "X-ClockodoApiKey", "location": "header"}, }, "resources": [ {"name": "entries", "endpoint": {"path": "v2/entries", "data_selector": "entries"}}, {"name": "users", "endpoint": {"path": "v2/users", "data_selector": "users"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="clockodo_pipeline", destination="duckdb", dataset_name="clockodo_data", ) load_info = pipeline.run(clockodo_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("clockodo_pipeline").dataset() sessions_df = data.entries.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM clockodo_data.entries LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("clockodo_pipeline").dataset() data.entries.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 Clockodo 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 Clockodo?

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

Available Pipelines