Skip to main content

Shift Assignment Endpoints

Audience​

Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling API behavior and boundaries.

Summary​

The native API exposes assignment creation and employee-scoped listing. No compatibility assignment route and no frontend assignment consumer were found.

Creation rules​

The employee identifier must be positive. The referenced shift must exist and be active. Missing start defaults to the current UTC date; supplied dates are normalized to dates. End is optional and inclusive, but cannot precede start. Any overlap with an active assignment returns a conflict.

Read behavior​

The employee-scoped query returns assignments ordered by effective start and enriches each result with a shift name when available.

Missing operations​

Update, end, deactivate, reactivate, delete, bulk assignment, shift swap, roster assignment, and department/team assignment endpoints are Not implemented.

Source References​

  • microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyQueries.cs
  • microservices/src/attendance-service/Domain/TimeOffice/EmployeeShiftAssignment.cs

See Also​

Keywords​

  • Workforce Scheduling API
  • Shift endpoints
  • Attendance policy API

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20