Attendance API

Summary

Attendance Service exposes direct bounded-context APIs, monolith-shaped compatibility APIs, Time Office APIs, and limited internal discovery. Gateway ownership remains transitional.

Audience

• Frontend and backend developers
• QA and support engineers, architects, security reviewers, and implementation partners

Overview

Scope and surfaces

• Direct / shadow: envelope-based Attendance and Time Office operations used for service validation and direct integration.
• Compatibility: bare-body contracts that preserve existing client behavior during gateway cutover.
• Internal / foundation: two discovery operations describing the bounded-context foundation.
• Primary: no separate Primary-only contract family exists; compatibility routes become the client-facing route when gateway ownership moves.

Bearer-authenticated downstream context and tenant context are expected for business operations. Exact per-route enforcement is not uniformly established by endpoint metadata and remains Requires confirmation. Authorization claims below are limited to capability checks visible in current source.

Verified endpoint inventory

Family	Documented operations
Attendance records and diagnostics	5
Attendance capture and punches	5
Submission and approval	4
Reopening	5
Employee profiles and roster	3
Payroll snapshots	2
Shifts	4
Shift assignments and effective policy	3
Weekly offs	2
Attendance policies and embedded rules	3
Compatibility Attendance	18
Compatibility Time Office	9
Internal/foundation discovery	2
Total documented	65

Maturity totals are 36 Direct operations, 27 Compatibility operations, and 2 Internal/Foundation operations. The 36 direct operations are also reachable through a gateway-recognized shadow/direct surface. Five development-only demo mappings are intentionally excluded from public route-level documentation. CLI backfill is not an HTTP API.

Documentation map

• API overview
• Authentication and context
• Response and error model
• Compatibility and routing
• OpenAPI and discovery
• Attendance records
• Attendance capture and punches
• Submission and approval
• Reopening
• Employee profiles
• Payroll snapshots
• Shifts
• Shift assignments
• Weekly offs
• Attendance policies
• Compatibility Attendance
• Compatibility Time Office
• API testing guide

Current limitations

There is no URL API version, committed OpenAPI artifact, policy-rule-only route family, delete-attendance operation, punch-correction operation, shift-assignment update/removal operation, device ingestion API, or HTTP backfill/maintenance API. Authentication enforcement, diagnostics access scope, and several privileged operations require end-to-end confirmation.

Source References

• microservices/src/attendance-service/Program.cs
• microservices/src/attendance-service/Api/AttendanceDirectEndpoints.cs
• microservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.cs
• microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
• microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs

Related Articles

• Attendance business overview
• Attendance technical overview

See Also

• Gateway interaction
• Security boundaries

Keywords

• Attendance API
• Direct API
• Compatibility API

Revision Information

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