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

# Get MicroVault shareholders

> Returns wallets in the current shareholder list and whether the list containing each wallet has been confirmed onchain.

Read the active shareholder root and the addresses represented by it.

<Note>
  MicroVaults are in private preview for enabled sandbox organizations on Ethereum Sepolia.
</Note>


## OpenAPI

````yaml swagger/swagger-combined.yaml GET /v2/microvaults/vaults/{vaultId}/shareholders
openapi: 3.0.0
info:
  title: Ground API
  description: Core API for Portfolio Wallets, gtokens, MicroVaults, and webhooks.
  version: 2.0.0
servers:
  - url: https://sandbox.groundtech.co
  - url: https://production.groundtech.co
security:
  - bearerAuth: []
tags:
  - name: System
    description: System health and utility endpoints.
  - name: Sandbox Faucets
    description: Sandbox-only test token faucets.
  - name: Portfolio Wallets
    description: >-
      Portfolio wallets with strategy allocation, deposits, withdrawals, and
      yield positions.
  - name: gVaults
    description: >-
      Direct access to gtokens with deposit access controls and optional fee
      wrappers.
  - name: MicroVaults
    description: >-
      Customer-owned onchain vaults with externally held ERC-20 shares. Private
      preview in sandbox on Ethereum Sepolia.
  - name: Webhook Endpoints
    description: Webhook endpoint management for portfolio wallet notifications.
paths:
  /v2/microvaults/vaults/{vaultId}/shareholders:
    parameters:
      - name: vaultId
        in: path
        required: true
        schema:
          $ref: '#/components/schemas/UuidV4'
        description: >-
          Ground identifier of the MicroVault. This is distinct from its onchain
          contract address.
    get:
      tags:
        - MicroVaults
      summary: List approved shareholders
      description: >-
        Returns wallets in the current shareholder list and whether the list
        containing each wallet has been confirmed onchain.
      operationId: getMicrovaultShareholders
      responses:
        '200':
          description: Approved shareholder addresses.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MicroVaultShareholdersResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    UuidV4:
      type: string
      format: uuid
      pattern: >-
        ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-4[0-9a-fA-F]{3}-[89aAbB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$
      example: 8f4c52d7-62ab-4db9-a964-92f481f6b851
    MicroVaultShareholdersResponse:
      type: object
      required:
        - shareholders
      properties:
        shareholders:
          type: object
          description: Current shareholder list and its onchain confirmation state.
          required:
            - version
            - root
            - confirmedAt
            - addresses
          properties:
            version:
              type: string
              nullable: true
              description: >-
                Onchain list version, or `null` before the first list is
                confirmed.
            root:
              allOf:
                - $ref: '#/components/schemas/MicroVaultBytes32'
              nullable: true
              description: >-
                Merkle root committed by the vault for the confirmed shareholder
                list.
            confirmedAt:
              type: string
              format: date-time
              nullable: true
              description: Time when this root was confirmed onchain.
            addresses:
              type: array
              description: >-
                Wallets in the latest shareholder list and whether that list is
                confirmed onchain.
              items:
                type: object
                required:
                  - address
                  - status
                properties:
                  address:
                    allOf:
                      - $ref: '#/components/schemas/NonzeroEvmAddress'
                    description: >-
                      Wallet eligible to hold and receive this MicroVault's
                      shares.
                  status:
                    type: string
                    enum:
                      - pending
                      - confirmed
                    description: >-
                      Whether the shareholder list containing this wallet has
                      been confirmed onchain.
      example:
        shareholders:
          version: '2'
          root: '0x4444444444444444444444444444444444444444444444444444444444444444'
          confirmedAt: '2026-09-10T18:40:00.000Z'
          addresses:
            - address: '0x76f8fc6667e239f83a547d4e16225d6a34f6fa22'
              status: confirmed
    MicroVaultBytes32:
      type: string
      pattern: ^0x[0-9a-fA-F]{64}$
      example: '0x1111111111111111111111111111111111111111111111111111111111111111'
    NonzeroEvmAddress:
      type: string
      description: >-
        Valid nonzero EVM EOA or contract address. Mixed-case values must use a
        valid EIP-55 checksum.
      minLength: 42
      maxLength: 42
      pattern: ^0x(?!0{40}$)[0-9a-fA-F]{40}$
      example: '0x3bf25a73a1f1033c2d50ac65f3c9d6a44123db81'
    AuthErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: Authentication or authorization error message.
        message:
          type: string
          nullable: true
          description: Additional auth middleware detail, when present.
        code:
          type: string
          nullable: true
          enum:
            - unauthenticated
            - forbidden
          description: >-
            Some auth and scope failures include a stable code; middleware
            errors may omit it.
  responses:
    Unauthorized:
      description: >-
        The request is missing a valid bearer token, or the token is invalid or
        expired.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AuthErrorResponse'
          example:
            error: Unauthenticated request
            message: Missing or invalid bearer token
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````