Returns the full history of extracted KYC verification records for a single user, ordered newest first. Each entry is the same curated view returned by GET /api/v1/kyc/detail/USER_ID, so this endpoint is useful for auditing repeated verification attempts or tracking how a user's verification state changed over time. Records are scoped to the authenticated client, so only verification records belonging to your own client are returned.

Authentication & access

• Requires a valid Bearer token (Authorization: Bearer <token>).
• Permission: kyc.users.read.
• Allowed roles: owner and operations. The developer role is not permitted.

Path parameters

• user_id (string, required) - the identifier of the user whose verification history you want to retrieve.

Behavior

• Results are filtered to the authenticated client; records belonging to other clients are never returned.
• Records are ordered by decision_at descending (records without a decision timestamp sort last), then by fetched_at descending.
• If the user has no verification records, the endpoint returns 200 with an empty records array. It does not return 404.

Response

A 200 response returns a VerificationDetailHistoryResponse object with a single field, records: an array of curated verification records (newest first). Each record contains:

Baseline fields (always present):

• status - verification record status (approved, declined, in_review, pending, expired, unknown).
• kind - verification kind (kyc).
• data_trusted - whether the extracted data is trusted.
• decision_at - decision timestamp, or null.
• fetched_at - timestamp the record was fetched.
• Identity fields: first_name, last_name, full_name, date_of_birth, nationality, document_type, document_issuing_country, document_expiry, gender (each may be null).
• Check results: liveness_status, liveness_score, face_match_status, face_match_score, nfc_status, poa_status, aml_status, aml_total_hits (each may be null). These check-result fields are populated only when the corresponding check was part of the verification performed; otherwise they are null.

Extended fields (present only when your client has been granted the corresponding visibility group):

• document_number - the document number.
• sof_questionnaire - source-of-funds answers.
• poa - extracted proof-of-address fields.
• aml_hits - AML hit details.
• documents - the list of downloadable document roles for the record.

When a visibility group has not been granted to your client, its fields are returned as null. The KYB-specific company fields (company_name, registration_number, registration_country, company_type, incorporation_date, registry_status, business_registry_details, business_key_people) are always null for KYC records.

Error responses

Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.