> ## 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.

# List MicroVault account records

List the MicroVault account records associated with your organization.

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


## OpenAPI

````yaml swagger/swagger-combined.yaml GET /v2/microvaults/customers
openapi: 3.0.0
info:
  title: Ground API
  description: Core API for Portfolio Wallets, gVaults, 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: App-specific Ground vaults with customer access and fee sharing.
  - 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/customers:
    get:
      tags:
        - MicroVaults
      summary: List MicroVault account records
      operationId: listMicrovaultCustomers
      responses:
        '200':
          description: MicroVault account records for the organization.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MicroVaultCustomerList'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    MicroVaultCustomerList:
      type: object
      required:
        - customers
      properties:
        customers:
          type: array
          items:
            $ref: '#/components/schemas/MicroVaultCustomer'
      example:
        customers:
          - id: 8ef3d494-7b6f-4df4-9d45-09f31196368f
            chainId: 11155111
            onchainCustomerId: '190025120042021478378651368413409605263'
            status: accepted
            authorityAddress: '0x1111111111111111111111111111111111111111'
            authorityEpoch: '1'
    MicroVaultCustomer:
      type: object
      required:
        - id
        - chainId
        - onchainCustomerId
        - status
        - authorityAddress
        - authorityEpoch
      additionalProperties: false
      properties:
        id:
          $ref: '#/components/schemas/UuidV4'
        chainId:
          type: integer
          example: 11155111
        onchainCustomerId:
          $ref: '#/components/schemas/MicroVaultUint256'
        status:
          type: string
          example: accepted
        authorityAddress:
          $ref: '#/components/schemas/NonzeroEvmAddress'
        authorityEpoch:
          $ref: '#/components/schemas/MicroVaultUint256'
    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.
    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
    MicroVaultUint256:
      type: string
      pattern: ^(0|[1-9][0-9]*)$
      description: >-
        Unsigned base-10 integer string. Asset and share amounts use token base
        units.
      example: '1000000'
    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'
  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

````