Returns a paginated list of employees with all their work schedule assignments - past, current and scheduled - as shown in the Work schedule section of the employee profile.

Ordering and effective periods. The history array is ordered by startDate ascending, from the oldest assignment to the most recent one, and it may contain entries whose startDate is in the future: those are schedule changes already planned. Each entry is effective from its own startDate until the startDate of the next entry, and the last entry has no end date. To determine which work schedule (and therefore which type, weeklyMinutes and dayShifts) applies on a given date, take the last entry whose startDate is earlier than or equal to that date.

Dates not covered by history. Two cases fall outside the array and are not returned by this endpoint:

• dates before the startDate of the first entry, and
• employees whose history is an empty array (no work schedule assignment was ever recorded).

In both cases the applicable working days come from the legacy *WorkingDay flags in GET /employees/work-schedules, and the applicable weekly hours from weeklyHours in GET /employees. Those legacy fields hold the values captured when the employee was created and are not updated when the work schedule changes, so they are only meaningful for the periods described above.

To resolve the contracted weekly minutes at one specific date without walking the array yourself, use GET /work-schedules/contracted-weekly-minutes - it already applies the rules above, legacy fallback included.

Limitations:

• The limit parameter accepts one of 25, 50, 100.
• The userId CSV filter accepts at most 15 ids.