Leave Holidays API
Summary
Four Direct operations provide Holiday list, create, update, and delete. No get-by-id, search, or date-range filter exists.
Audience
Frontend/backend developers, QA, Leave/Attendance administrators, and implementation partners.
Reference Content
Maturity: Direct / Transitional. Authentication: expected. Authorization: administration scope Requires confirmation in extracted service. Tenant: required for mutations and filters all persistence.
| Operation | Method/route | Request | Response/status | Behavior |
|---|---|---|---|---|
| List Holidays | GET /leave/holidays | None | 200 HolidayDto[] | Ordered by date; read-only. |
| Create Holiday | POST /leave/holidays | HolidayRequest | 200 HolidayDto; 400 missing name | Adds tenant Holiday; audit; no domain event. |
| Update Holiday | PUT /leave/holidays/{id} | Route id + HolidayRequest | 200 DTO; 404 missing; 400 missing name | Replaces name/date/type; audit. |
| Delete Holiday | DELETE /leave/holidays/{id} | Route id | 200 plain success; 404 missing | Removes Holiday; audit. |
Request fields: name, date, optional type (defaults to Paid when blank). Response fields: id, name, date string, and type.
{"name":"Synthetic Company Holiday","date":"2032-06-15","type":"Paid"}
No optional/regional semantics or active field exists. Paid/unpaid is free text with confirmed downstream meaning. Holiday changes affect later Leave-day calculation when policy exclusion is enabled; no balance, Workflow, Attendance mutation, or Leave event occurs. Compatibility CRUD is documented separately.
Source References
microservices/src/leave-service/Api/LeaveEndpoints.csmicroservices/src/leave-service/Application/Dtos.csmicroservices/src/leave-service/Application/LeaveWorkflows.csmicroservices/src/leave-service/Domain/Leave/CalendarEntities.cs
Related Articles
See Also
Keywords
- Leave API
- Leave Holidays API
- Endpoint reference
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly