Skip to main content

Recruitment Diagnostics API

Summary​

Four host or native operations expose service information, shallow health, tenant counts, and outbox state.

Audience​

Developers, QA and support engineers, implementation partners, architects, and security reviewers.

Reference Content​

MethodRelative routeClassification
GET/Host foundation service information
GET/healthHost shallow health
GET/recruitment/health-dataTenant-scoped entity counts
GET/recruitment/outboxBounded outbox evidence

The service root is the only confirmed Recruitment response using the shared ApiResponse<T> envelope. The health operation has no dependency probes. Health-data and outbox are operational/foundation surfaces, not proof of readiness.

Diagnostics authorization, production exposure, outbox-data visibility, readiness/liveness separation, and dependency health Require confirmation.

Response and Errors​

Successful Result-based operations return direct values. Confirmed failure mappings are 400 validation, 404 missing resource, and 409 conflict with a message object. Direct queries and diagnostics return their source-defined shapes.

Requires confirmation​

Endpoint authorization, production exposure, privacy controls, ownership, operational limits, and compatibility parity require confirmation.

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/Api/RecruitmentEndpoints.cs
  • microservices/src/shared-kernel/Extensions/EndpointRouteBuilderExtensions.cs
  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs

See Also​

Keywords​

  • Recruitment API
  • Source-backed endpoint reference

Revision Information​

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