Leave API Compatibility and Routing

Summary

Gateway selects monolith or Leave Service ownership for compatibility traffic; direct, shadow, cutover, rollback, and ESS behavior reuse the verified contracts.

Audience

Frontend/backend developers, QA, architects, DevOps, support, and implementation partners.

Overview

Compatibility Leave, Holiday, weekly-off, workspace, and balance routes preserve existing client shapes while service extraction proceeds. Shadow mode is routing behavior, not a separate endpoint inventory. ESS composes direct Leave queries/commands behind gateway-owned aggregate routes.

Client-contract differences include monolith authorization/scope behavior, response shapes outside the Leave subset of the HR workspace, and possible calendar ownership. Exact routing toggles, private route tables, service addresses, and operational cutover commands are excluded.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/scripts/smoke-leave.ps1

Related Articles

• Leave API
• Response and error model

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave API Compatibility and Routing
• Integration

Revision Information

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