Clockify API
★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey11 EndpointsREST
For Agents
Log time entries, create projects and tasks, manage workspace members and clients, and generate invoices in Clockify on behalf of a user.
Use for: I need to log a two-hour time entry against a project, Create a new project under a Clockify workspace, List all clients in my workspace, Generate an invoice for a client based on tracked time
Not supported: Does not handle payroll, expense reimbursement, or accounting ledgers — use for time tracking, project time entries, and invoice generation only.
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.
Install Jentic One Beta
Connect the Clockify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clockify API, 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.
1
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 | sh2
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 instanceJentic 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 Clockify API.
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
Patterns agents use Clockify API for, with concrete tasks.
★ 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.
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.
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.
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.
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
11 endpoints — jentic publishes the only available openapi specification for clockify api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Clockify API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution rights — the X-Api-Key header is injected at request time and the raw key never enters the agent's context window.
Intent-based discovery
Agents search Jentic by intent (e.g., 'log a time entry') and Jentic returns the matching Clockify operations with their input schemas, so the agent can call the right endpoint without reading docs.
Time to first call
Direct Clockify integration: 1-2 days for auth, workspace discovery, and error handling. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Clockify API through Jentic.
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 at https://app.jentic.com/sign-up.
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 the MAXsystem vault 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.
GET STARTED