Trigger a screening
Screenings are auto-triggered on candidate ingestion by default; use this endpoint to (re)trigger one manually — for example after contact attempts were exhausted and you have a corrected phone number. Returns 409 if a screening is already in progress for the candidate.
Authentication
Path parameters
Organization ID (org_...).
Candidate ID (cand_...).
Headers
Unique key (e.g. a UUID) making this POST safe to retry. Replays within 24 hours return the original response without repeating side effects.
Response
Screening ID (scr_...).
The candidate’s external_ref, echoed for correlation.
Simplified partner-facing screening status. Flow: pending_contact → contacting → terminal (completed, no_answer_exhausted, declined_recording, opted_out, withdrawn). When completed, see outcome for passed vs failed_knockout. The candidate’s full v4 stage slug rides along as stage.
Candidate lifecycle stage slug (v4). Rides along on screenings as stage for partners who want full lifecycle granularity; most integrations only need the simplified partner screening status.
Outbound contact attempts made so far (voicemails and no-answers included).
Set only when the screening status is completed.
Structured result, present once the screening status is completed. Signals are item-level only — the Partner API intentionally exposes no composite or overall score.

