Leave API
Summary
Leave Service exposes 19 direct-group operations and 14 compatibility operations. One direct-group operation is an Internal Workflow callback; no employee-profile, carry-forward, or encashment HTTP family exists.
Audience
Frontend/backend developers, QA and support engineers, architects, security reviewers, and implementation partners.
Overview
Scope and surfaces
- Direct: 18 public business/query operations grouped under the Leave bounded context.
- Internal: one Workflow completion callback.
- Compatibility: 14 monolith-shaped operations for existing Leave, calendar, and HR balance clients.
- Shadow: gateway validation mode reuses existing operations; it does not add distinct endpoints.
- Foundation: carry-forward, encashment, and employee projection have no public HTTP operations.
Bearer authentication is expected at the gateway/service boundary. Tenant context is required for mutations and tenant-scoped behavior. Per-route extracted-service authorization metadata is not uniformly confirmed, so final enforcement remains Requires confirmation / Transitional. Workflow delegation changes decision behavior without changing request routes.
Verified endpoint inventory
| Family | Operations |
|---|---|
| Direct Leave requests | 3 |
| Direct approval/rejection | 1 |
| Direct cancellation | 1 |
| Direct balances | 3 |
| Direct Leave types | 2 |
| Direct policies | 1 |
| Direct Holidays | 4 |
| Direct weekly offs | 2 |
| Direct timeline | 1 |
| Internal Workflow callback | 1 |
| Compatibility Leave | 5 |
| Compatibility calendar | 6 |
| Compatibility balances/workspace | 3 |
| Total | 33 |
Documentation map
- API overview, authentication/context, responses/errors, routing, and OpenAPI
- Requests, approval/rejection, cancellation, balances, types, policies, Holidays, weekly offs, timeline, and Workflow callbacks
- Compatibility Leave, calendar, and balances
- API testing guide
Current limitations include absent versioning, no committed OpenAPI artifact, transitional authorization/routing, unbounded list operations, stored-but-unenforced policy fields, and incomplete foundation capabilities.
Source References
microservices/src/leave-service/Program.csmicroservices/src/leave-service/Api/LeaveEndpoints.csmicroservices/src/gateway-api/Program.cs
Related Articles
See Also
Keywords
- Leave API
- Leave API
- Integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly