Recruitment Compatibility Requisitions API

Summary

Six compatibility operations manage requisitions and position records.

Audience

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

Reference Content

Method	Relative route	Input
POST	/api/hr-suite/recruitment/requisitions	RecruitmentPositionDto
POST	/api/hr-suite/recruitment/requisitions/{id}/approve	Numeric identifier
POST	/api/hr-suite/recruitment/requisitions/{id}/reject	RequisitionDecisionDto
POST	/api/hr-suite/recruitment/positions	RecruitmentPositionDto
PUT	/api/hr-suite/recruitment/positions/{id}	RecruitmentPositionDto
PATCH	/api/hr-suite/recruitment/positions/{id}/status	PositionStatusDto

Requisition creation and position creation are distinct compatibility commands over native concepts. Numeric identifiers are compatibility identities. No compatibility requisition list/detail route is mapped outside the workspace response.

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

Related Articles

• Recruitment API documentation
• Compatibility and routing

See Also

• Recruitment technical documentation
• Recruitment module

Keywords

• Recruitment API
• Source-backed endpoint reference

Revision Information

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