Skip to main content

Recruitment Job Requisitions API

Summary​

Three native operations create and decide requisitions.

Audience​

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

Reference Content​

MethodRelative routeInputSuccess
POST/recruitment/requisitionsCreateRequisitionInputRequisitionDto
POST/recruitment/requisitions/{id}/approveRoute identifierRequisitionDto
POST/recruitment/requisitions/{id}/rejectRejectRequisitionInputRequisitionDto

Create accepts title, organizational references, opening count, experience, compensation-range fields, location, employment type, hiring-manager reference, and description. Decisions can return validation, missing-resource, or conflict outcomes. Workflow-managed requisitions restrict direct decisions. There is no native requisition list or detail route; the workspace query carries requisition collections.

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/RecruitmentEndpoints.cs
  • microservices/src/recruitment-service/Application/Dtos.cs
  • microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs

See Also​

Keywords​

  • Recruitment API
  • Source-backed endpoint reference

Revision Information​

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