---
title: "List IDV Sessions for a User"
method: GET
path: "/v2.01/{ClientId}/users/{UserId}/identity-verifications"
tags: ["idvSessions"]
---

# List IDV Sessions for a User

`GET /v2.01/{ClientId}/users/{UserId}/identity-verifications`

Retrieve key details of all hosted KYC/KYB sessions attempted for a user. To view the full details of a specific session, including checks and verified data, use [GET View an IDV Session](/api-reference/idv-sessions/view-idv-session).

[Read more about hosted KYC/KYB](/guides/users/verification/hosted) **→**

## Path parameters

- `ClientId` string, required
- `UserId` string, required

## Headers

- `Authorization` string, required

## Response `200`

Success

- ListIDVSessionsForAUserResponse
  - `Id` string — Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
  - `Status` string — The status of the overall IDV Session: - `PENDING` – Session created. The `HostedUrl` is valid for completion, regardless of whether the user has started or submitted the session. - `REVIEW` – One or more automated checks was neither successful nor refused, so the session was sent for manual review by Mangopay's teams. This temporary state is only applicable to Legal users and can transition to `REFUSED` or `VALIDATED`. - `VALIDATED` – - The session was validated and the User became KYC/KYB verified (indicated by the User object's `KYCLevel`). When the `Status` changes to `VALIDATED`, the [verified data](/guides/users/verification/hosted/natural#verified-data) in `Checks.Data` is used to replace existing data in the User object. - `REFUSED` – The session was refused and the User is not KYC/KYB verified. The `Checks.CheckStatus` shows which checks were `REFUSED` and the `Checks.Reasons` shows the [refused reason types](/guides/users/verification/hosted/refusals) and comment (which is custom text in the case of manual review for Legal users). - `EXPIRED` – The IDV Session expired and can no longer be used. By default, this happens 7 days after the `CreationDate`. However, if the IDV Session contains the liveness step and that step has been started (the QR code was generated), the session instead expires 1 hour after the liveness step started. The IDV Session contains the liveness step for Natural users, Soletrader users, and Business/Organization users on the legacy integrated flow. In the multi-session PSC flow, the main IDV Session never contains the liveness step (so it always follows the 7-day rule) – the liveness check is performed in each PSC Session instead, which follows the same 7-day/1-hour rule independently. - `OUT_OF_DATE` – The IDV Session is not valid because the user's KYC/KYB verification status was [downgraded](/guides/users/verification/downgrade) by Mangopay.
  - `CreationDate` integer — Unix timestamp (UTC) of the date and time the object was created.
  - `LastUpdate` integer — Unix timestamp (UTC) of the date and time the session was last updated.

---

[API](https://skmtc.dev/mangopay/apis/api-reference.md) · [All operations](https://skmtc.dev/mangopay/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mangopay/api-reference/revisions/fafbd0c69654/schema)