canonical: https://jentic.com/apis/clockodo.com/clockodo # Clockodo API Documentation 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). ## For AI agents Track work entries, manage customers, projects, services, and absences in Clockodo, and pull project reports for billing. ## Scope Does not handle payroll calculation, tax filing, or accounting ledgers - use for time tracking, absence management, and project reporting only. ## Capabilities - 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 - Generate project reports with billable, billed, and unbilled splits - Configure hourly rates and lump-sum services per customer or project - Control access groups and per-user permissions across resources ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Entry** — Time entries logged by users against customers, projects, and services - **Customer** — Client records with billing details and project associations - **Project** — Engagements with budgets, rates, and subprojects - **Service** — Service catalogue items priced per hour or as lump sums - **Absence** — Vacation, sick leave, and other employee absences - **HolidayQuota** — Per-user holiday allowances and balances - **ProjectReport** — Aggregated billing and effort reports per project - **Rate** — Hourly billing rates by user, project, or service ## Why Jentic - **Setup:** Wiring Clockodo by hand means assembling its X-ClockodoApiUser and X-ClockodoApiKey header pair, mapping versioned endpoints for entries, absences, and reports, and handling retries yourself against my.clockodo.com/api. Through Jentic you install once, import the Clockodo API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Clockodo's write targets like a time entry carry their identifiers in the request body rather than the URL path, so scope the agent to the operations it needs, such as creating and reading entries. You choose which operations are in that set, so absence or project-report operations are not included unless you add them. - **Credential handling:** Your Clockodo user and key header pair is stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a Clockodo time entry', and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without reading the large reference. ## Related APIs - **Clockify API** — Global time tracking platform with simpler primitives and a generous free tier. - **Close CRM API** — Sales CRM that pairs with Clockodo to attribute time spent to deals and customers. - **Clockwork Recruiting API** — Executive search platform that benefits from per-engagement time tracking. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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. ### Can I limit what my agent is allowed to do with the Clockodo API? Yes. Because you run Jentic One yourself, your own rules decide which Clockodo operations and credentials the agent may use. You can scope it to just the operations it needs, such as creating and reading time entries via POST and GET /v2/entries, and leave out absence, holiday-quota, or project-report operations unless you explicitly add them. Since Clockodo write targets carry their identifiers in the request body rather than the URL path, this operation-level allowlist is how you control what the agent can call.