Leave Weekly Offs API

Summary

Two Direct operations read and atomically replace the tenant weekly-off day-name collection.

Audience

Frontend/backend developers, QA, Leave/Attendance administrators, and implementation partners.

Reference Content

Maturity: Direct / Transitional. Authentication: expected. Authorization: administration scope Requires confirmation. Tenant: required for replacement and tenant-filtered list.

Operation	Method/route	Request	Response/status	Behavior
List weekly offs	GET /leave/weekly-offs	None	200 WeeklyOffDto[]	Ordered persisted collection; read-only.
Replace weekly offs	PUT /leave/weekly-offs	JSON string[]	200 WeeklyOffDto[]; missing tenant 400	Removes existing tenant rows and adds trimmed, nonblank, case-insensitive distinct values; audit; no domain event.

Example request: ["Saturday","Sunday"]. Success: [{"day":"Saturday"},{"day":"Sunday"}]. No day-name validity check is implemented by this command.

Replacement affects future policy-enabled Leave calculation. Attendance has overlapping weekly-off ownership and the gateway may route this compatibility family according to current Time Office ownership. No create-one/delete-one endpoints, employee scope, effective dates, rotation, or active state exist.

Source References

• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Domain/Leave/CalendarEntities.cs
• microservices/src/gateway-api/Program.cs

Related Articles

• Leave API
• Authentication and context
• Response and error model

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave Weekly Offs API
• Endpoint reference

Revision Information

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