Skip to main content

Attendance API Compatibility and Routing

Summary​

The gateway can move Attendance-record and Time Office compatibility ownership independently while direct/shadow surfaces remain available for validation.

Audience​

API consumers, architects, QA, DevOps and support engineers, and implementation partners.

Routing flow​

Compatibility Attendance preserves existing array, bare DTO, string, and error shapes. Compatibility Time Office preserves legacy shift and weekly-off contracts; policy compatibility is additive because no matching monolith policy API exists. Direct routes use envelopes and may expose additional service-owned diagnostics or foundation operations.

Cutover assets support direct-service testing, gateway-route testing, parity comparison, independent Time Office ownership, go/no-go evaluation, and rollback. Exact routing-toggle names, internal destinations, and operational commands are intentionally excluded.

Clients must not assume direct and compatibility bodies are interchangeable. Conflict status differs, route availability depends on ownership, and policy/effective-diagnostics capabilities do not have complete monolith equivalents. No compatibility endpoint is marked deprecated in source.

Source References​

  • microservices/src/gateway-api/Program.cs
  • microservices/src/attendance-service/Api/AttendanceDirectEndpoints.cs
  • microservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.cs
  • microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
  • microservices/scripts/compare-attendance-shift-parity.ps1
  • microservices/scripts/attendance-shift-cutover-go-no-go.ps1

See Also​

Keywords​

  • Attendance API
  • Attendance API Compatibility and Routing

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly