Recruitment Interviews API

Summary

Native APIs list and schedule interviews, while a public token route returns interview context.

Audience

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

Reference Content

Method	Relative route	Input or output
GET	/recruitment/interviews	Array of InterviewDto
POST	/recruitment/interviews	ScheduleInterviewInput to InterviewDto
GET	/recruitment/public/interviews/{token}	PublicInterviewDto

Scheduling binds candidate/opening references, round information, interviewer metadata, schedule, mode, and location/link information. Public lookup uses an opaque token. No native reschedule, cancel, delete, or dedicated detail operation is mapped.

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/Api/RecruitmentPublicEndpoints.cs
• microservices/src/recruitment-service/Application/Dtos.cs
• microservices/src/recruitment-service/Application/Commands/InterviewCommands.cs

Related Articles

• Recruitment API documentation
• Response and error model

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