> ## Documentation Index
> Fetch the complete documentation index at: https://guides.saber.money/llms.txt
> Use this file to discover all available pages before exploring further.

# Get User Details (v1)

> Fetch user's details, including KYC and Bank Account status



## OpenAPI

````yaml /openapi-v1.json get /api/v1/user/client_user
openapi: 3.1.0
info:
  title: Saber Money API (v1)
  version: v1
  description: >-
    ## Authentication


    There is no standalone API-key auth — every request must be **signed**. An
    API key by itself authenticates nothing. Each call requires four headers
    together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey +
    timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required —
    keyed with your API secret), `X-Timestamp` (unix seconds), and
    `X-Request-Id` (any unique string per request). The signature must be
    computed by a client script; there is no way to derive it by hand. Use the
    HMAC Generator flow to compute valid values for manual testing.


    ## Common Authentication Errors


    - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id
    invalid","success":false}

    - **Invalid Secret**: {"error_code":6090,"message":"invalid
    secret","success":false}

    - **Timestamp (Older than 10 secs)**:
    {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false}
servers:
  - url: https://api.saber.money
security: []
paths:
  /api/v1/user/client_user:
    get:
      tags:
        - User Operations
      summary: Get User Details (v1)
      description: Fetch user's details, including KYC and Bank Account status
      operationId: get-user-details-v1
      parameters:
        - name: X-Api-Key
          in: header
          required: true
          description: Your API key (configured in credentials)
          schema:
            type: string
        - name: X-Signature
          in: header
          required: true
          description: >-
            HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256
            of `apiKey + timestamp` (or `apiKey + timestamp + userId` when
            X-User-Id is required), keyed with your API secret. The HMAC
            Generator flow computes this for you.
          schema:
            type: string
        - name: X-Timestamp
          in: header
          required: true
          description: >-
            Unix timestamp in seconds (auto-generated) Unix seconds, e.g.
            `Math.floor(Date.now() / 1000)`. Must match the timestamp used in
            the X-Signature computation.
          schema:
            type: string
        - name: X-Request-Id
          in: header
          required: true
          description: >-
            Unique request identifier (auto-generated) Any unique string per
            request, e.g. a UUID.
          schema:
            type: string
        - name: X-User-Id
          in: header
          required: true
          description: User UUID (set above)
          schema:
            type: string
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: object
                    properties:
                      user_uuid:
                        type: string
                      client_user_id:
                        type: string
                      kyc_status:
                        type: string
                      bank_accounts:
                        type: array
                        items:
                          type: object
                      email:
                        type: string
                      phone:
                        type: string
              example:
                success: true
                data:
                  user_uuid: 3faced19-20c7-48b8-952b-6143c8c198d2
                  client_user_id: client_reference
                  kyc_status: Verified
                  bank_accounts:
                    - account_holder_name: First name last name
                      ifsc_code: ABCD000555511
                      status: APPROVED
                      account_number: 55XXXXX2001
                      bank_id: c41f7d27-781c-41da-b74c-278fe7202af5
                  email: email@email.com
                  phone: '+911234567890'

````

## Related topics

- [Get Transaction Details (v1)](/api-reference/offramp/get-transaction-details-v1.md)
- [Get Beneficiary Details (v1)](/api-reference/onramp/get-beneficiary-details-v1.md)
- [Get Buy Transaction Details (v1)](/api-reference/onramp/get-buy-transaction-details-v1.md)
- [Get Sell Transaction Details (v1)](/api-reference/offramp/get-sell-transaction-details-v1.md)
- [Get Crypto Deposit Transaction Details (v1)](/api-reference/wallet-operations/get-crypto-deposit-transaction-details-v1.md)