Skip to main content

Recruitment Compatibility API

Summary​

The 28-operation compatibility surface preserves existing numeric identifiers and monolith-shaped contracts.

Audience​

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

Reference Content​

Compatibility inventory​

FamilyOperations
Workspace1
Requisitions3
Positions3
Public positions/application2
Candidates5
Interviews and feedback3
Offers3
Public interviews/feedback2
Public offers3
Onboarding2
Resume download1
Total28

Compatibility DTOs use settable properties and existing defaults; response records preserve the portal's module-record and typed metadata shape. Adapters translate numeric compatibility identities, labels, and commands to native application services.

Byte-for-byte runtime parity, error parity, authorization parity, and retirement criteria are Requires confirmation. The source comment states input-shape intent but is not a substitute for automated contract comparison.

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/Api/RecruitmentCompatEndpoints.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatContracts.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatCommands.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatQueries.cs

See Also​

Keywords​

  • Recruitment API
  • Source-backed endpoint reference

Revision Information​

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