Skip to main content

Holiday and Weekly-Off 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​

Workforce Scheduling exposes weekly-off operations in native and compatibility forms. It exposes no holiday endpoint. Holiday APIs belong to another service boundary and are Not implemented in this slice.

Native semantics​

The native update requires at least one supplied day. Each day may be a weekday name or supported numeric value. Duplicate days are rejected. Existing rules are activated or deactivated, new rules are added, and omitted days remain unchanged.

Compatibility semantics​

The compatibility request is a bare list of day names representing the complete active set. Blank entries are skipped, duplicates collapse through set semantics, invalid days fail validation, omitted days are deactivated, and an empty list clears all active weekly offs.

Read semantics​

Native reads include stored rules and active states. Compatibility reads return active days only using the legacy DTO shape.

Ownership​

Gateway cutover can move the compatibility weekly-off family to Attendance Service independently. When not moved, its owner can remain the current legacy or Leave boundary. Authoritative production ownership requires confirmation.

Source References​

  • microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
  • microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
  • microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.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