Read submitted applicant data for a KYC check
/v1/kyc/checks/{id}/applicantRequires an API client bearer token.
The case's submitted applicant data, narrowed to the custody `review` purpose — the human-adjudication slice, including contact fields the evaluation engines never see. Every read is reported to pii-vault's audit pipeline (`access_recorded: true`) on a best-effort basis — an audit-publish failure never fails the read itself, so this is not an unconditional guarantee — attributed to the identity-kyc service principal, not to the individual console user who made the request.
Parameters
Path parameters
| Name | Required | Description |
|---|---|---|
| id | required |
Example
curl https://api.rigid.fi/v1/kyc/checks/{id}/applicant \
-H "Authorization: Bearer $RIGID_API_TOKEN"Responses
200The check's submitted applicant data.
+ show properties− hide properties
No properties.
400Validation error
401Authentication required
403Forbidden
404KYC check not found, or no applicant data has been submitted yet
410Applicant data crypto-erased under the retention policy
500Internal server error