Recruitment Timeline and Audit API
Summary
Two native query operations expose audit and timeline evidence.
Audience
Developers, QA and support engineers, implementation partners, architects, and security reviewers.
Reference Content
| Method | Relative route | Query behavior |
|---|---|---|
| GET | /recruitment/audit | Optional entity-type filter and bounded take |
| GET | /recruitment/timeline | Bounded take ordered by occurrence |
Responses are direct arrays of selected evidence fields rather than named DTO types. These are application/operational evidence, not a governed security-audit API. Endpoint authorization, retention, redaction, pagination, and export ownership 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/RecruitmentEndpoints.csmicroservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/recruitment-service/Infrastructure/Persistence.cs
Related Articles
See Also
Keywords
- Recruitment API
- Source-backed endpoint reference
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly