Skip to main content

API Architecture

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

Attendance Service owns the canonical API implementation. Native routes expose canonical identifiers and standard envelopes. Compatibility routes preserve legacy request and response shapes. The gateway decides whether legacy paths remain with their existing owner or move to Attendance Service.

API classifications

ClassificationVerified purposeMaturity
NativeCanonical shift, weekly-off, policy, assignment, resolution, audit, and timeline operationsFoundation/Partial
CompatibilityExisting frontend-shaped shifts, weekly offs, and policy administrationTransitional
GatewayRuntime selection of the current owner for compatibility pathsTransitional
Shared diagnosticsService information and healthFoundation

Frontend Shift Management consumes compatibility shifts and policy administration. Other frontend screens also read weekly offs. No frontend consumer of the native assignment endpoints was found.

Ownership boundary

The endpoint catalog intentionally excludes the broader Attendance API, demo endpoints, attendance-domain discovery, Leave holiday endpoints, and framework-generated documentation assets. Those belong to adjacent modules or framework infrastructure.

Current maturity

The API is not a complete workforce scheduling contract. It lacks roster publication, rotations, bulk assignments, availability, swaps, and assignment maintenance beyond creation and listing.

Source References

  • microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
  • microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
  • microservices/src/gateway-api/Program.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx

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