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

See pricing

Retrieving employee apps data via API

The Employee Apps endpoint returns application and website usage summaries available to the authenticated integration. Respect workspace monitoring settings and permission scope when using this data.

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 date range. Use optional type filters when the integration needs app-only or website-only results.

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

Example response

Results are summarized by tracked duration and may include the productivity category configured in Worklix.

{
  "data": [
    { "name": "Figma", "type": "app", "tracked_seconds": 6240, "category": "productive" },
    { "name": "docs.example.com", "type": "website", "tracked_seconds": 3180, "category": "neutral" }
  ]
}

Privacy and scope

Only request activity data that is necessary for the integration purpose. Keep employee-facing policy, workspace permissions and role boundaries aligned with how the data will be used.

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.