Skip to main content

Compatibility 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​

Nine compatibility endpoints reproduce the observable shapes used by existing consumers: four shift operations, two weekly-off operations, and three policy operations. Exact routes and methods appear only in the endpoint catalog.

Shape preservation​

Shift DTOs use compatibility identity and legacy fields. Weekly-off responses contain active day rows. Policy endpoints use canonical policy DTOs but return bare bodies. Errors are bare strings or values rather than the native standard envelope. Successful compatibility delete is plain text.

Behavioral preservation​

Compatibility shift delete deactivates assignments with the shift. Weekly-off update replaces the whole active set. Textual overtime rules are parsed into a numeric threshold and rendered back to legacy wording.

Security mismatch​

The monolith requires authentication for these controller families. The extracted compatibility adapter only rejects authenticated non-administrators on mutations and trusts unauthenticated upstream calls.

Classification​

Compatibility is Transitional. Parity tools exist, but production cutover and retirement criteria require confirmation.

Source References​

  • microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
  • microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.cs
  • microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatContracts.cs
  • Controllers/ShiftsController.cs
  • Controllers/WeeklyOffsController.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