Recruitment Documents API
Summary
Five operations manage candidate document references and download candidate or offer files.
Audience
Developers, QA and support engineers, implementation partners, architects, and security reviewers.
Reference Content
| Method | Relative route | Behavior |
|---|---|---|
| POST | /recruitment/candidates/{id}/documents | Store content and add reference |
| GET | /recruitment/candidates/{id}/documents | Return reference metadata |
| GET | /recruitment/candidates/{id}/documents/{documentId}/download | Download referenced content |
| GET | /recruitment/offers/{id}/download | Download offer letter |
| GET | /api/recruitment/candidates/{candidateId}/resume/download | Compatibility resume download |
Recruitment stores references, not document bytes. Delete, metadata update, retention, malware scanning, and explicit document authorization routes 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.csmicroservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.csmicroservices/src/recruitment-service/Application/Dtos.csmicroservices/src/recruitment-service/Infrastructure/DocumentServiceClient.cs
Related Articles
See Also
Keywords
- Recruitment API
- Source-backed endpoint reference
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly