Leave OpenAPI and Discovery

Summary

Runtime Swagger/OpenAPI discovery is configured, but no committed Leave OpenAPI JSON/YAML artifact exists.

Audience

Developers, QA, architects, and implementation partners.

Overview

The service registers endpoint discovery, OpenAPI generation, and Swagger UI at runtime. Use only an approved environment and its authorized discovery mechanism. No static OpenAPI JSON/YAML was found in the repository, and this epic does not generate one.

The project contains source comments but does not configure a generated XML documentation file for Swagger enrichment. No API-versioning package, version segment, or version negotiation is present. The checked-in HTTP file is only scaffold material and does not describe the current Leave API.

A generated, reviewed reference artifact is a future opportunity after authorization, response, and compatibility contracts stabilize.

Source References

• microservices/src/leave-service/Program.cs
• microservices/src/leave-service/leave-service.csproj
• microservices/src/leave-service/leave-service.http

Related Articles

• Leave API
• Response and error model

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave OpenAPI and Discovery
• Integration

Revision Information

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