canonical: https://jentic.com/apis/clockify.me/clockify

# Clockify API

Jentic publishes the only available OpenAPI specification for Clockify API, keeping it validated and agent-ready. Clockify is a time tracking and timesheet management service that lets teams log work hours, organize work into projects and tasks, manage workspace members and clients, and generate invoices. The API exposes core resources for users, workspaces, time entries, projects, tasks, clients, and invoices, with regional endpoints in EU Central and US East alongside the global host. Authentication uses a workspace API key passed in the X-API-Key header.

## For AI agents

Log time entries, create projects and tasks, manage workspace members and clients, and generate invoices in Clockify on behalf of a user.

## Scope

Does not handle payroll, expense reimbursement, or accounting ledgers - use for time tracking, project time entries, and invoice generation only.

## Capabilities

- Log time entries against projects and tasks within a workspace
- Create and list billable projects with client associations
- Add team members to a workspace and read membership lists
- Generate invoices for tracked work tied to clients
- List clients and tasks scoped to a workspace
- Retrieve the authenticated user profile and accessible workspaces

## Use cases

### Automated Time Entry Logging

Capture work hours against the right project without manual timesheet entry. Agents can post time entries to a workspace via POST /workspaces/{workspaceId}/time-entries with start time, end time, billable flag, and project assignment, so a chat or calendar integration can convert a meeting or commit message into a logged entry. This removes the end-of-week timesheet rush and keeps billing data current.

Example prompt: Create a time entry in workspace W1 for project P1 from 09:00 to 11:00 today, marked billable, with description 'Client kickoff call'.

### Project and Client Setup

Spin up a new client engagement end to end. An agent can create a project under the workspace via POST /workspaces/{workspaceId}/projects, link it to a client, list existing clients to avoid duplicates, and confirm tasks are in place - turning a sales handoff into a billable project structure in seconds rather than hours of manual setup.

Example prompt: Create a project named 'Acme Q3 Engagement' linked to client C42 in workspace W1, with hourly billable rate $150.

### Invoice Generation From Tracked Time

Convert tracked hours into client-ready invoices. Using POST /workspaces/{workspaceId}/invoices, an agent assembles invoice line items for a billing period, ties them to a specific client, and triggers the invoice creation flow - replacing manual reconciliation between timesheets and accounting tools.

Example prompt: Generate an invoice for client C42 in workspace W1 covering all billable time entries between 2026-05-01 and 2026-05-31.

### AI Agent Time Tracking Assistant

Embed Clockify time tracking inside an AI assistant that watches calendar events and chat activity. Through Jentic, the agent searches for the right operation by intent, loads the schema, and posts entries on the user's behalf - no docs scraping or hand-coded HTTP clients needed. Credentials stay isolated in Jentic's vault, so the agent never sees the raw API key.

Example prompt: Search Jentic for 'log a time entry', load the Clockify create time entry schema, and execute it for a 30-minute Slack call with project P7.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /workspaces/{workspaceId}/time-entries | Create a time entry |
| GET | /workspaces | List accessible workspaces |
| GET | /workspaces/{workspaceId}/projects | List projects in a workspace |
| POST | /workspaces/{workspaceId}/projects | Create a new project |
| GET | /workspaces/{workspaceId}/clients | List clients |
| POST | /workspaces/{workspaceId}/invoices | Create an invoice |
| GET | /user | Get current authenticated user |

## Key resources

- **Time Entries** — Create and manage logged work intervals tied to projects and tasks
- **Workspaces** — Top-level container for users, projects, clients, and reports
- **Projects** — Billable or non-billable work units linked to clients
- **Tasks** — Sub-units of projects for granular tracking
- **Clients** — Customer records that projects and invoices are billed against
- **Invoices** — Billing documents generated from tracked time
- **Users** — Workspace members with roles and access controls

## Why Jentic

- **Setup:** Wiring Clockify by hand means managing its API-key request header, choosing the right host across its global, EU, and US regional endpoints, and handling retries yourself. Through Jentic you install once, import the Clockify API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Clockify puts the workspace id in the URL path (/workspaces/{workspaceId}/...), so a rule can pin your agent to one workspace: it can log time entries and read projects there and nothing else. You choose the operations it may call, so creating projects or invoices are not included unless you add them.
- **Credential handling:** Your Clockify API key is stored once, encrypted, by your own Jentic One instance and injected as the API-key request header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'log a time entry', and Jentic returns the matching Clockify operation with its input schema, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clockodo API** — European time-tracking platform with similar project, task, and invoicing primitives.
- **Close CRM API** — Sales CRM that pairs with Clockify to log billable activity against deals.
- **Clockwork Recruiting API** — Executive search platform that benefits from project-time logging during candidate engagements.

## FAQ

### Why is there no official OpenAPI spec for Clockify API?

Clockify does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clockify API 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 Clockify API use?

Clockify uses an API key passed in the X-API-Key header. You generate the key from your Clockify profile settings. With Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so agents never see the raw secret.

### Can I create time entries programmatically with the Clockify API?

Yes. Use POST /workspaces/{workspaceId}/time-entries with start, end, billable, projectId, and description fields. The endpoint returns the created entry with its assigned id, ready to surface back in your UI or notify a Slack channel.

### What are the rate limits for the Clockify API?

Clockify enforces a soft limit of roughly 50 requests per second per workspace, with stricter limits on report endpoints. The OpenAPI spec does not encode these limits, so handle 429 responses with exponential backoff. Jentic execution surfaces 429s to your agent so it can retry cleanly.

### How do I generate an invoice through Jentic?

Search Jentic for 'create an invoice in clockify', load the schema for POST /workspaces/{workspaceId}/invoices, then execute with the workspace id, client id, and date range. Run pip install jentic, then use client.search, client.load, and client.execute to drive the flow.

### Does the Clockify API support multiple regions?

Yes. The spec defines four servers: the global endpoint at api.clockify.me, a reports endpoint at reports.api.clockify.me, EU Central at euc1.api.clockify.me, and US East at use2.api.clockify.me. Choose the region that matches your workspace residency.

### Can I limit what my agent is allowed to do with the Clockify API?

Yes. Because you run Jentic One yourself, your own rules decide which Clockify operations and credentials the agent may use. Clockify puts the workspace id in the URL path, such as /workspaces/{workspaceId}/time-entries, so you can pin the agent to a single workspace and let it only log time entries and read projects there. Creating projects with POST /workspaces/{workspaceId}/projects or generating invoices with POST /workspaces/{workspaceId}/invoices stays off limits unless you explicitly add those operations to what the agent may call.