API Documentation
The Pro API is read-only: pull employees, time entries, and projects into your own tools. Starting and stopping timers stays in the Windows desktop companion—not the public API.
Authentication
Create a team API key (clk_…) in Settings on a Pro workspace. Send it as Authorization: Bearer or x-api-key. Keys are shown once at creation and stored hashed.
curl "$API_BASE/v1/employees" \
-H "Authorization: Bearer clk_YOUR_KEY"List employees
Read the workforce roster for reconciliation with HR or client billing tools.
curl "$API_BASE/v1/employees" \
-H "Authorization: Bearer clk_YOUR_KEY"Export time entries (timesheets)
Fetch team time entries with optional date, project, and employee filters. This is the integration path for billable hours—not a start/stop timer API.
curl "$API_BASE/v1/time-entries?from=2026-01-01&to=2026-01-31" \
-H "Authorization: Bearer clk_YOUR_KEY"
curl "$API_BASE/v1/employees/EMPLOYEE_ID/time-entries" \
-H "x-api-key: clk_YOUR_KEY"List projects
Map project IDs used in timers to names in your own systems.
curl "$API_BASE/v1/projects" \
-H "Authorization: Bearer clk_YOUR_KEY"Starting and stopping timers
Session start, pause, and stop happen in the desktop app (authenticated user JWT). The public /v1 API does not expose write endpoints for timers—by design, so integrations remain export-oriented and safer.
Was this helpful?
Ready to try it?
Start a free workspace or compare plans before you invite the team.