New Worklix brings monitoring, time tracking and collaboration into one workforce platform.

See pricing

Starting a project and task via API

Use the Start Work endpoint when a trusted system needs to begin a Worklix project or task timer for a specific employee. The workflow should have explicit employee and project ownership.

Keep API credentials server-side.

Do not expose production tokens in browser code, public repositories or shared client-side configuration.

Request

Send the employee, project and optional task IDs in the request body. Use a source string so audit logs can identify which integration initiated the action.

POST https://api.worklix.com/v1/work-sessions/start

{
  "employee_id": "emp_1042",
  "project_id": "prj_302",
  "task_id": "tsk_22",
  "source": "internal-ops"
}

Example response

The response returns the active session identifier and start time.

{
  "data": {
    "session_id": "ses_7c31",
    "employee_id": "emp_1042",
    "project_id": "prj_302",
    "task_id": "tsk_22",
    "started_at": "2026-09-15T00:10:00Z",
    "status": "running"
  }
}

Operational safeguards

Confirm the employee is allowed to track the project and handle existing active sessions before starting a new one. Keep retries idempotent so network failures do not create duplicate sessions.

Was this article helpful?
Build with clearer API context

Know the resource first.Then build the connection.

Use the Worklix API guides to plan authentication, data flow and production ownership before your integration reaches live workforce data.