Recruitment OpenAPI and Discovery

Summary

Endpoint discovery and Swagger generation are registered, but versioning, XML documentation output, and a committed OpenAPI artifact are absent.

Audience

Developers, QA and support engineers, implementation partners, architects, and security reviewers working with Recruitment APIs.

Reference Content

Confirmed implementation:

• Endpoint API explorer and Swagger generation are registered.
• Swagger middleware and its interactive UI are enabled by the host.
• Endpoint names and tags provide discovery metadata.
• The service root returns a shared service-information envelope.
• A source-controlled HTTP request collection supports manual discovery.

No API versioning package or versioned route convention was found. The project does not enable XML documentation generation, and no generated OpenAPI document is committed. Production Swagger exposure and governance Require confirmation.

Requires confirmation

Production exposure, authorization policy, ownership, compatibility parity, operational limits, and version governance require confirmation.

Source References

• microservices/src/recruitment-service/Program.cs
• microservices/src/recruitment-service/recruitment-service.csproj
• microservices/src/recruitment-service/recruitment-service.http
• microservices/src/shared-kernel/Extensions/EndpointRouteBuilderExtensions.cs

Related Articles

• Recruitment API documentation
• Recruitment technical documentation

See Also

• Recruitment module
• Recruitment business documentation

Keywords

• Recruitment API
• OpenAPI and Discovery

Revision Information

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