Stage: Registration and sourcing

Registration and sourcing: getting candidates into Jadiroon. Candidates register themselves on your careers page; through the API, a job board, a sourcing tool or your ERP's talent pool can add them too.

Resources

Typical flow

1. Create the candidate with POST /api/v1/candidates, or many at once with POST /api/v1/candidates/bulk (each row may carry an https cvUrl; Jadiroon downloads and stores the CV privately).
2. Add the candidate to an opening: see Hiring.
3. Read the CV with GET /api/v1/candidates/{id}/cv (streamed; Jadiroon never hands out a storage link). It needs recruitment.candidate.contact, because the file shows contact details.
4. Subscribe to candidate.created and candidate.updated to see self-registered candidates.

Rules worth knowing

• Candidate email, phone and national ID are masked in responses and webhook payloads unless the integration holds recruitment.candidate.contact; without it PATCH leaves them unchanged.
• A duplicate person is refused (409 conflict, details.reason duplicate_person).
• Candidates are never hard-deleted through the API. A candidate who deletes their own account sends candidate.deleted and leaves a tombstone.