Create and manage projects and track billable time entries in Clockify via the REST API
domain: docs.clockify.me · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using the X-Api-Key header with your Clockify API key.
POST to /workspaces/{workspaceId}/projects with a JSON body specifying the project name, client ID (optional), billable flag, and color to create a new project.
Optionally POST tasks under the project at /workspaces/{workspaceId}/projects/{projectId}/tasks to create sub-items for granular time tracking.
POST to /workspaces/{workspaceId}/time-entries with start, end, projectId, taskId, and billable fields to log a completed time entry on behalf of a user; use the userId path if creating entries for other workspace members.
GET /workspaces/{workspaceId}/reports/summary (Reports API) with a billable filter to produce a billable hours summary grouped by project or client.
Use the PATCH endpoint to update existing time entries when corrections are needed; provide only the fields that need to change.
Known gotchas
The Clockify Reports API has a separate base URL (reports.api.clockify.me) from the main REST API; mixing base URLs for reporting vs. data-write operations is a common integration mistake.
Billable rates and project budgets are workspace-level settings that may require a paid plan; attempting to set billable rates via the API on a free workspace silently ignores the field.
Time entry start and end must be ISO 8601 UTC strings; local-time strings without timezone offset are rejected or misinterpreted.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?