Skip to main content

Shift 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 shift family supports list, create, update, and soft deletion. Compatibility provides the same operation families using legacy identities, payloads, and response bodies. Exact method/route entries appear only in the endpoint catalog.

Native behavior​

Lists can include inactive records. Creation and update accept canonical time, grace, standard-hours, overtime, night-shift, and activation fields. Delete deactivates the row and returns the resulting shift. An active assignment produces a conflict.

Validation​

Times must parse in the accepted culture-independent formats and cannot be equal. Name is required by the aggregate and active names are checked case-insensitively for uniqueness. Grace and hour values have domain bounds. Crossing-midnight windows can derive night classification.

Compatibility behavior​

Only active shifts are returned. Legacy payloads omit standard hours and use a textual overtime rule. Standard hours come from the tenant default policy or fallback during create and remain unchanged during update. Grace is clamped to a non-negative value. Delete deactivates both the shift and active assignments instead of returning a conflict.

Maturity​

CRUD is Implemented. Hard deletion is Not implemented by the canonical service. Concurrency-safe name uniqueness requires confirmation.

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/Shift.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