Skip to main content

Attendance Weekly Offs API

Summary​

Two direct operations retrieve and upsert tenant weekly-off day rules.

Audience​

Frontend/backend developers, QA engineers, implementation partners, and support engineers.

Reference Content​

Authentication: Bearer and Time Office administration context expected; exact direct enforcement requires confirmation. Tenant: required. Maturity: Direct/Shadow, Transitional.

OperationMethod and public routeContractResponses and behaviorSafe example
List weekly offsGET /attendance/weekly-offsNo parameters/body200 ApiResponse<WeeklyOffRuleDto[]>; read-onlyGET /attendance/weekly-offs → data:[]; handled tenant failure → 400.
Update weekly offsPUT /attendance/weekly-offsWeeklyOffUpdateRequest200 ApiResponse<WeeklyOffRuleDto[]>; 400 invalid; upserts supplied days, audit/timeline, no Attendance event{"days":[{"dayOfWeek":"Friday","isActive":true}]} using a fictional policy choice → 200; duplicate/invalid/empty days → 400.

Request contains days; each entry contains dayOfWeek and isActive. Day names or supported numeric day representations are parsed. At least one day is required, and duplicate days in a request are rejected. Days omitted from the direct request are left unchanged; this is not a full replacement despite the application method name.

Responses contain rule id, dayOfWeek, and isActive. Rules are tenant-scoped. No separate create/delete route, employee scope, shift-specific recurrence, effective date, or holiday/Leave precedence endpoint exists. Compatibility weekly-off update has different whole-set semantics and is documented separately.

Source References​

  • microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
  • microservices/src/attendance-service/Application/TimeOffice/ShiftPolicyDtos.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyQueries.cs

See Also​

Keywords​

  • Attendance API
  • Attendance Weekly Offs API

Revision Information​

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