Skip to main content

Recruitment Offer Approval API

Summary​

Two native operations approve or reject an offer.

Audience​

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

Reference Content​

MethodRelative routeInput
POST/recruitment/offers/{id}/approveOfferDecisionInput
POST/recruitment/offers/{id}/rejectRejectOfferInput

Approval records approver evidence and optional notes; rejection requires a reason. Offer approval is not delegated to Workflow Service. Approval thresholds, policy enforcement, separation of duties, and authorization are Not implemented.

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/OfferCommands.cs

See Also​

Keywords​

  • Recruitment API
  • Source-backed endpoint reference

Revision Information​

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