---
title: "Get an employee’s schedule on a date"
method: GET
path: "/companies/{company}/work-schedules/employee/{employee}"
tags: ["Work Schedules"]
---

# Get an employee’s schedule on a date

`GET /companies/{company}/work-schedules/employee/{employee}`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/work-schedules/employee/{employee}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Resolve the work schedule in effect for an employee on a day; `date` (`Y-m-d`) is optional and defaults to today.
- Returns the schedule, not the assignment.
- 404 `schedule_assignment_not_found` if none is in effect (or the employee belongs to another company); 422 for an invalid `date`.

## Path parameters

- `company` string, uuid, required
- `employee` string, uuid, required

## Query parameters

- `date` string, date, nullable

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` EmployeeSchedule, required: The work schedule currently in effect for an employee on a given date, resolved from the employee’s open assignment. `id` is the UUID v7 of the underlying work schedule (not of the assignment).
    - `id` string, uuid, required: UUID v7 of the work schedule currently in effect for the employee.
    - `object` 'employee_work_schedule', required: Always `employee_work_schedule`.
    - `name` string, required: Human-readable name of the schedule.
    - `mode` 'validated' | 'real_clocking', required: Mode of the schedule: `validated` or `real_clocking`.
    - `week_pattern` object[], required: Weekly pattern: one entry per configured weekday with its ordered, non-overlapping time ranges. A weekday absent from the list (or with an empty `ranges`) is a rest day.
      - `day` integer, required: ISO 8601 weekday (1 = Monday … 7 = Sunday).
      - `ranges` object[], required: Ordered, non-overlapping time ranges worked that day (empty = rest day).
        - `start` string, required: Range start time (HH:MM, 24h).
        - `end` string, required: Range end time (HH:MM, 24h).
    - `weekly_hours` number, float, required: Total weekly hours derived from the pattern.
    - `effective_from` string, date, required: Date the schedule became effective for the employee, in `Y-m-d`.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)