Skip to main content

Leave Calendar Compatibility API

Summary

Six compatibility operations expose Holiday CRUD and weekly-off read/replace using existing client routes.

Audience

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

Reference Content

Maturity: Compatibility / Transitional. Authentication: monolith requires authenticated calls; gateway/service expectation applies after cutover. Authorization: monolith permits authenticated reads and administrator mutations; extracted parity Requires confirmation. Tenant: required.

OperationMethod/public routeBody/parametersResponse/statusBehavior
List HolidaysGET /api/holidaysNone200 Holiday rowsTenant list; no filter/side effect.
Create HolidayPOST /api/holidaysHoliday name/date/type200 row; 400 invalid; 403 monolith non-adminAudit in extracted service; no Leave event.
Update HolidayPUT /api/holidays/{id}Route id + Holiday body200 row; 404; 400/403 as owner enforcesReplaces fields.
Delete HolidayDELETE /api/holidays/{id}Route id200 plain success; 404; possible 403Removes entry.
List weekly offsGET /api/weekly-offsNone200 day rowsRead-only.
Replace weekly offsPUT /api/weekly-offsJSON day-name array200 day rows; possible 400/403Replaces tenant collection; exact day validation absent in extracted command.

Holiday fields and examples are in Holidays; weekly-off fields/examples are in Weekly Offs. No date-range Holiday lookup, optional/regional calendar operation, per-employee weekly-off operation, or individual weekly-off CRUD exists.

Weekly-off routing can resolve to Attendance Service before Leave Service depending on current Time Office ownership. This overlap is Transitional and must be included in gateway parity testing.

Source References

  • microservices/src/leave-service/Api/LeaveEndpoints.cs
  • Controllers/HolidaysController.cs
  • Controllers/WeeklyOffsController.cs
  • microservices/src/gateway-api/Program.cs

See Also

Keywords

  • Leave API
  • Compatibility
  • Leave Calendar Compatibility API

Revision Information

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