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

See pricing

Retrieving employee data via API

The Employee endpoint returns identity, employment status and selected work settings for a single employee. Add a date when your workflow needs day-specific tracking context.

Keep API credentials server-side.

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

Request

Pass the employee ID in the resource path. Use the optional date query parameter in YYYY-MM-DD format.

GET https://api.worklix.com/v1/employees/emp_1042?date=2026-09-14

Example response

The response keeps employee identity separate from date-specific work context so downstream systems can use only the fields they need.

{
  "data": {
    "id": "emp_1042",
    "name": "Jordan Lee",
    "email": "jordan@example.com",
    "status": "active",
    "department": "Support",
    "workday": {
      "date": "2026-09-14",
      "tracked_seconds": 26740,
      "attendance_state": "present"
    }
  }
}

Parameters

The employee ID is required. The date parameter is optional and defaults to the workspace-local current date when date-specific context is supported for the request.

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.