Record a disposition on a screening candidate
/v1/screenings/{screeningId}/candidates/{candidateId}/dispositionRequires an API client bearer token.
Records a reviewer verdict (true_match or false_positive) on a surfaced candidate. Dispositions are append-only and STICKY: the latest disposition for a (subject, list entry) pair takes effect immediately in the pending-review queue and suppresses or confirms the same entry on any future re-screen, without requiring a re-screen to apply. A true_match is FOUR-EYES: it only becomes effective once a second, distinct reviewer files a second true_match for the same pair — until then it stays effectively pending, with awaiting_confirmation surfaced on read; the same reviewer attempting to confirm their own true_match gets 409 four_eyes_required. false_positive needs no second reviewer and is always latest-wins, including as the correction path for a mistaken true_match. Requires an Idempotency-Key header and a named human reviewer.
Parameters
Header parameters
| Name | Required | Description |
|---|---|---|
| Idempotency-Key | required | Client-chosen. An identical retry with the same key returns the stored response; reusing the key with a different payload returns 409. |
Request body
Example
curl -X POST https://api.rigid.fi/v1/screenings/{screeningId}/candidates/{candidateId}/disposition \
-H "Authorization: Bearer $RIGID_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"disposition": "true_match",
"reviewer_name": "string"
}'Responses
201Disposition recorded.
400Validation error
401Authentication required
403Forbidden
404Candidate not found
409Idempotency-Key reused with a different payload, or four_eyes_required — the same reviewer cannot confirm their own true_match
500Internal server error