Request a document re-capture on a referred KYC check
/v1/kyc/checks/{id}/recaptureRequires an API client bearer token.
Reopens a referred case for one more document scan instead of forcing an approve/reject decision on what it already has: transitions referred -> evaluating, opens the case's re-capture window, records a recapture_requested decision naming the human reviewer, and mints a fresh capture-session token for the applicant. Emits no kyc.check.completed — nothing has completed. Only a referred case may be re-captured.
Parameters
Path parameters
| Name | Required | Description |
|---|---|---|
| id | required |
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/kyc/checks/{id}/recapture \
-H "Authorization: Bearer $RIGID_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"reviewer_name": "string"
}'Responses
200The re-capture window is open; a fresh capture session was minted.
+ show properties− hide properties
400Validation error
401Authentication required
403Forbidden
404No such check
409Idempotency-Key reused with a different payload
429Too many KYC writes from this caller — see Retry-After
500Internal server error