Skip to main content

Recruitment Applications API

Summary

Two public native operations expose open positions and accept candidate applications.

Audience

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

Reference Content

MethodRelative routeInput or output
GET/recruitment/public/openingsArray of PublicOpeningDto
POST/recruitment/public/openings/{openingId}/applyApplyCandidateInput to CandidateDto

Application input includes candidate identity/contact fields, experience, source, optional notes, and optional resume metadata/content. The command performs duplicate application checks and can store resume bytes through Document Service. No standalone application list, detail, update, withdrawal, or deletion operation is implemented.

Public exposure, abuse controls, consent, retention, upload limits, and authorization Require confirmation.

Response and Errors

Successful Result-based operations return their DTO directly. Confirmed failures map to 400 validation, 404 missing resource, or 409 conflict with a message object. Authorization-specific outcomes are not defined by these endpoints.

Requires confirmation

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

Source References

  • microservices/src/recruitment-service/Api/RecruitmentPublicEndpoints.cs
  • microservices/src/recruitment-service/Application/Dtos.cs
  • microservices/src/recruitment-service/Application/Commands/CandidateCommands.cs
  • microservices/src/recruitment-service/Application/Queries/RecruitmentQueries.cs

See Also

Keywords

  • Recruitment API
  • Source-backed endpoint reference

Revision Information

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