Skip to main content

Attendance Integration 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 scheduling surface exposes one effective-policy diagnostic read plus audit and timeline diagnostics. It does not expose attendance record, punch, approval, reopen, or payroll snapshot operations; those belong to the Attendance API.

Resolution output​

The response identifies the winning value source, referenced shift and policy when present, shift start, standard hours, overtime threshold, grace, status-rule presence, and weekly-off state. Optional probe hours can return the status that current rules would calculate.

Diagnostics​

Audit and timeline reads accept optional entity filters and a requested result size. Query code bounds the number returned. These are application diagnostics, not health probes.

Boundary​

The broader Attendance API consumes the resolver internally during attendance calculation. It is documented in the Attendance module and is excluded from the Workforce endpoint total.

Source References​

  • microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyQueries.cs
  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.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