# Get KYC Verification Status

Retrieves the current status of the Know Your Customer (KYC) verification step for the specified onboarding process. Provides details on liveness, face match, and document checks based on the results from the identity verification provider.

Endpoint: GET /onboarding/{onboarding_process_ulid}/kyc-status
Version: 1.1.0
Security: user_bearer_auth

## Path parameters:

  - `onboarding_process_ulid` (string, required)
    The unique identifier (ULID) for the user's onboarding process.
    Example: "01ARZ3NDEKTSV4RRFFQ69G5FAV"

## Response 200 fields (application/json):

  - `user_id` (string, required)
    User id.
    Example: "27c7e9af-b519-4bec-a9c1-c7fd51aad8b6"

  - `status` (string, required)
    The overall status of a verification check or the entire process.
    Enum: "Approved", "Rejected", "Processing", "RequiresReview", "NotPerformed", "Error"

  - `message` (string)
    Message explaining the rejection type.
    Enum: "Retry available", "Do not retry"

## Response 401 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."

## Response 404 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."

## Response 500 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."