Clockodo API Documentation

Name: Clockodo API Documentation API
Brand: Clockodo API Documentation
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbasic, apiKey143 EndpointsREST

For Agents

Track work entries, manage customers, projects, services, and absences in Clockodo, and pull project reports for billing.

Install Jentic One Beta

Connect the Clockodo API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clockodo API Documentation, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Clockodo API Documentation API.

Record and update time entries against customers, projects, and services

Manage customer and project hierarchies including subprojects

Track employee absences, holiday quotas, and overtime carryover

GET STARTED

Start building with Clockodo API Documentation API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Clockodo API Documentation, keeping it validated and agent-ready. Clockodo is a German time tracking and project planning service used by agencies, freelancers, and SMBs to record working hours, manage absences, and produce project and billing reports. The REST API exposes 143 operations across resources like entries, customers, projects, services, absences, rates, and access groups, with versioned paths (v2, v3, v4) replacing legacy endpoints. Authentication is HTTP Basic combined with header-based user and key tokens (X-ClockodoApiUser, X-ClockodoApiKey).

Use Cases

Patterns agents use Clockodo API Documentation API for, with concrete tasks.

★ Billable Entry Capture for Agencies

Agencies billing by the hour need accurate, attributable time entries. Through POST /v2/entries an agent records the duration, customer, project, service, and billable flag, while GET /v2/entries supports filtering by customer or date range. This replaces spreadsheet timesheets and lets ops teams close the billing month from chat instead of compiling per-employee CSVs.

Create a billable entry for customer 1234, project 5678, service 'Consulting' for 2.5 hours on 2026-06-09 with note 'discovery workshop'.

Absence and Holiday Management

HR teams in EU companies need auditable absence records aligned to statutory holiday quotas. The Absence, HolidayQuota, and HolidayCarryover endpoints let an agent submit a leave request, check remaining quota, and roll unused days forward at year end. The flow keeps the official ledger inside Clockodo while the agent surfaces approvals via Slack or Teams.

Submit a vacation absence for user 42 from 2026-08-01 to 2026-08-12 and confirm remaining holiday quota for the year.

Project Profitability Reporting

Project managers need to know whether a fixed-price engagement is still in the green. Calling the ProjectReport endpoints returns hours billed, hours unbilled, budget consumed, and rate-by-service breakdowns — replacing manual reconciliation between time entries and the rate card. An agent can summarise the data weekly and flag projects exceeding budget.

Generate a project report for project 9001 covering 2026-04-01 to 2026-06-30 and highlight services where actual hours exceeded budgeted hours.

AI Agent Time Tracking via Jentic

Wire Clockodo into an AI assistant that runs over the user's calendar and IDE activity. Through Jentic, the agent searches by intent, loads the right entry-creation schema, and posts entries on the user's behalf. Credentials stay isolated in Jentic's vault; the user's Clockodo API user and key never leave the secure boundary.

Search Jentic for 'log a clockodo entry', load the create-entry schema, and post a 45-minute coding session to project 9001 service 'Development'.

Key Endpoints

143 endpoints — jentic publishes the only available openapi specification for clockodo api documentation, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/entries

Create a time entry

GET

/v2/entries

List time entries with filters

GET

/v3/customers

List customers

GET

/v4/absences

List employee absences

GET

/v2/holidaysQuota

Get holiday quotas

GET

/v2/projectsreports

Generate project reports

POST

/v2/entries

Create a time entry

GET

/v2/entries

List time entries with filters

GET

/v3/customers

List customers

GET

/v4/absences

List employee absences

GET

/v2/holidaysQuota

Get holiday quotas

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Clockodo's user+key header pair is stored encrypted in the Jentic vault (MAXsystem). Agents trigger calls without ever seeing X-ClockodoApiUser or X-ClockodoApiKey in their context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a clockodo entry') and Jentic returns the matching operations with their schemas, so the agent does not need to read 143-endpoint docs to find the right path.

Time to first call

Direct Clockodo integration: 3-5 days to map versioned endpoints and absence quotas. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using Clockodo API Documentation API through Jentic.

Why is there no official OpenAPI spec for Clockodo API Documentation?

Clockodo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clockodo API Documentation via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Clockodo API use?

Clockodo combines HTTP Basic Auth with two custom headers — X-ClockodoApiUser (your account email) and X-ClockodoApiKey (your generated API key). Through Jentic, both values are stored encrypted in the MAXsystem vault and injected at execution time so agents never see the raw credentials.

Can I record billable time entries with the Clockodo API?

Yes. POST to /v2/entries with customers_id, projects_id, services_id, billable, time_since, and time_until. The endpoint returns the created entry id and the calculated duration, ready to surface in dashboards or downstream invoicing.

What are the rate limits for the Clockodo API?

Clockodo applies a soft fair-use cap around 60 requests per minute per API key. The spec does not encode exact limits, so handle 429 responses with backoff. Jentic surfaces the 429 to your agent so it can retry without dropping the operation.

How do I generate a project report through Jentic?

Run pip install jentic, then search for 'clockodo project report'. Jentic returns the ProjectReport operation; load its schema and execute with projects_id and a date range. The agent receives billed, unbilled, and budget-utilisation totals as JSON.

Does the Clockodo API handle absences and holiday quotas?

Yes. The Absence, HolidayQuota, HolidayCarryover, and OvertimeCarry tags expose endpoints to submit leave, check remaining quotas, and roll balances forward. This is an EU-focused feature aligned to German labour law conventions.

Clockodo API Documentation

Connect the Clockodo API Documentation to your agent

Capabilities

Start building with Clockodo API Documentation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs