Leave Policies API

Summary

One Direct read-only operation lists Leave policies. No create, update, delete, activation, or assignment HTTP operation exists.

Audience

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

Reference Content

Maturity: Direct / Foundation. Authentication: expected. Authorization: list access Requires confirmation. Tenant: tenant-filtered query.

Operation	Method/route	Parameters/body	Response/status	Behavior
List Leave policies	GET /leave/policies	None	200 LeavePolicy[]	Ordered by Leave type; read-only; no audit/event/side effect.

Response fields are id, tenantId, leaveType, accrualPerMonth, maxCarryForward, minNoticeDays, maxConsecutiveDays, excludeHolidays, excludeWeeklyOffs, allowNegativeBalance, and isActive. Safe examples should redact tenant identity; an empty result is [].

Only active policy lookup and calendar exclusions are confirmed in request calculation. Accrual, carry-forward maximum, notice, duration, negative-balance, assignment, and effective-date enforcement are absent or incomplete. Half-day metadata is on LeaveType, not LeavePolicy.

Source References

• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Domain/Leave/LeaveConfig.cs

Related Articles

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

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave Policies API
• Endpoint reference

Revision Information

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