Leave API Overview

Summary

ASP.NET Core Minimal APIs bind DTOs and invoke scoped command/query services directly, with compatibility groups preserving existing client shapes.

Audience

Developers, QA, architects, support, and implementation partners.

Overview

Direct and compatibility routes share LeaveCommands, LeaveQueries, and DTO mappings. There is no MediatR dispatch. Mutations use Result<T> translation; queries generally return plain JSON bodies. Leave public responses do not use a common ApiResponse<T> envelope. The Attendance client internally consumes an envelope from Attendance, which is not the Leave response contract.

Authentication middleware, tenant context, runtime Swagger/OpenAPI, Attendance conflict checking, optional Workflow delegation, and gateway routing are composed at runtime. No API version segment or versioning library is present. Monolith coexistence remains Transitional.

Source References

• microservices/src/leave-service/Program.cs
• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs

Related Articles

• Leave API
• Response and error model

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave API Overview
• Integration

Revision Information

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