Retrieving employee projects and apps data via API

Use the Employee Work Context endpoint when a workflow needs project allocation and app/website summaries in one response instead of coordinating two independent reads.

Keep API credentials server-side.

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

Request

Provide the employee ID and bounded date range.

GET https://api.worklix.com/v1/employees/emp_1042/work-context?from=2026-09-14&to=2026-09-14

Example response

The response groups project and application context under the same employee and requested period.

{
  "data": {
    "employee_id": "emp_1042",
    "projects": [{ "id": "prj_302", "tracked_seconds": 18420 }],
    "apps": [{ "name": "Figma", "tracked_seconds": 6240 }]
  }
}

When to use separate endpoints

Use the dedicated project or app endpoint if your system needs only one dataset. Smaller responses are easier to cache, retry and reason about in production.

Was this article helpful?

Retrieving employee projects and apps data via API

Request

Example response

When to use separate endpoints

Know the resource first.Then build the connection.