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

# Get wallets by customer

> Retrieve a customer’s wallets and IBANs to use in financial operations.

## Endpoint

`GET /api/v2.1/wallets/customer/{customerId}`

<Note>
  This endpoint requires `X-Forwarded-From` and a device header. The backend accepts any of:
  `deviceId`, `X-Device-Id`, `device-id`.
</Note>

## Sample cURL

```bash theme={null}
curl --request GET \
  --url 'https://sandbox.finhub.cloud/api/v2.1/wallets/customer/{customerId}?customerType=B2C' \
  --header 'Authorization: Bearer <ACCESS_TOKEN>' \
  --header 'X-Tenant-Id: <TENANT_ID>' \
  --header 'Accept: application/json' \
  --header 'X-Forwarded-From: <FORWARDED_FROM>' \
  --header 'deviceId: <DEVICE_ID>'
```

```bash theme={null}
curl --request GET \
  --url 'https://sandbox.finhub.cloud/api/v2.1/wallets/customer/{customerId}?customerType=B2B' \
  --header 'Authorization: Bearer <ACCESS_TOKEN>' \
  --header 'X-Tenant-Id: <TENANT_ID>' \
  --header 'Accept: application/json' \
  --header 'X-Forwarded-From: <FORWARDED_FROM>' \
  --header 'deviceId: <DEVICE_ID>'
```

## Response Example

```json theme={null}
{
  "code": 200,
  "data": [
    {
      "id": "558ad9af-0482-471f-9385-5a943b80f6d2",
      "walletId": "558ad9af-0482-471f-9385-5a943b80f6d2",
      "customerId": "2dac1793-ab48-420c-b0b5-01292302e188",
      "name": "B2C Product General Purpose Wallet",
      "walletType": "b2c_product_general_purpose_wallet",
      "status": "ACTIVE",
      "currency": "EUR",
      "balance": "0.00",
      "availableBalance": "0.00",
      "iban": "LT213320011000055860"
    },
    {
      "id": "f9f66497-ef59-446b-9b32-34391b27c928",
      "walletId": "f9f66497-ef59-446b-9b32-34391b27c928",
      "customerId": "2dac1793-ab48-420c-b0b5-01292302e188",
      "name": "B2C Master General Purpose Wallet",
      "walletType": "b2c_master_general_purpose_wallet",
      "status": "ACTIVE",
      "currency": "EUR",
      "balance": "0.00",
      "availableBalance": "0.00"
    }
  ],
  "message": "Success"
}
```

<Note>
  After customer activation, poll this endpoint until wallets with IBAN appear. The IBAN is typically assigned to the Product General Purpose Wallet.
</Note>

## Missing Headers Error Example

```json theme={null}
{
  "code": 500,
  "data": {
    "deviceId_accepted": [
      "deviceId",
      "X-Device-Id",
      "device-id"
    ],
    "missingHeaders": [
      "X-Forwarded-From",
      "deviceId"
    ]
  },
  "message": "Missing required header(s)"
}
```


## OpenAPI

````yaml openapi.yaml GET /api/v2.1/wallets/customer/{customerId}
openapi: 3.1.0
info:
  title: Business BFF API
  version: 1.0.0
  description: Backend for Frontend - Business Panels Orchestration Layer
servers:
  - url: https://sandbox.finhub.cloud
    description: Sandbox Environment
security: []
tags:
  - name: AML
    description: Anti-Money Laundering checks and transaction monitoring
  - name: Admin - Consent Management
    description: Operations for managing consent templates and definitions
  - name: B2B Customer - Organization
    description: B2B organization registration and management
  - name: B2C Customer - Individual
    description: Individual customer registration and lifecycle management
  - name: BFF Admin - Tenant Initialization
    description: Lazy tenant initialization for fast startup
  - name: Catalog Hierarchy
    description: Hierarchical catalog management APIs
  - name: Catalog-Process Mapping
    description: APIs for catalog-process relationship management
  - name: Consent
    description: Payment consent creation and approval
  - name: Draft Management
  - name: External Events
    description: Kafka-to-HTTP bridge event ingestion and query
  - name: FinCard Virtual - Webhooks
    description: FinCard Virtual Card Webhook receiver
  - name: FinCard Virtual Account
    description: FinCard Virtual Card Account API proxy
  - name: FinCard Virtual Card Holder
    description: FinCard Virtual Card Holder API proxy
  - name: FinCard Virtual Cards
    description: FinCard Virtual Card API proxy
  - name: FinCard Virtual Common
    description: FinCard Virtual Card Common API proxy
  - name: FinCard Virtual Wallet
    description: FinCard Virtual Card Wallet API v2 proxy
  - name: FinTrans - Operations
    description: Financial transaction operations
  - name: Internal Webhooks
    description: Internal service-to-service webhook trigger (HMAC-secured)
  - name: MFE Preload
    description: MFE preload endpoints for SSR optimization
  - name: MFE Registry
    description: MFE Registry management endpoints
  - name: Payment Consent Management
    description: Operations for managing payment consents and validation
  - name: Person
    description: Person details for process context
  - name: Products
    description: Product Catalog Management API
  - name: Reference Data
    description: Shared reference data (countries, etc.)
  - name: Tenant Lifecycle
    description: Tenant mode transitions and lifecycle management
  - name: Tenant Registration
    description: Self-registration and tenant onboarding
  - name: Transfers
    description: Transfer prepare/execute aliases for muse-proxy compatibility
  - name: Verification
    description: Customer verification (KYC/KYB/AML) management
  - name: Wallet
    description: Wallet operations and balance management
  - name: Webhooks
    description: Webhook subscription and delivery management
paths:
  /api/v2.1/wallets/customer/{customerId}:
    get:
      tags:
        - Wallet
      summary: Get customer wallets
      description: >-
        Retrieves all wallets for a specific customer. Use customerType=B2C for
        individuals, B2B for organizations (default). Poll after activation
        until wallets appear.
      parameters:
        - name: customerId
          schema:
            type: string
            format: uuid
            examples:
              - 00000000-0000-0000-0000-000000000000
          in: path
          required: true
        - name: customerType
          in: query
          schema:
            type: string
            default: B2B
        - name: X-Tenant-ID
          in: header
          required: true
          schema:
            type: string
            example: tenant-demo-001
        - name: X-Forwarded-For
          in: header
          required: true
          description: Client IP address
          schema:
            type: string
            example: 127.0.0.1
        - name: X-Forwarded-From
          in: header
          required: true
          description: Client source identifier
          schema:
            type: string
            example: client-app
        - name: platform
          in: header
          required: true
          description: Client platform
          schema:
            type: string
            example: mobile
        - name: deviceId
          in: header
          required: true
          description: Device identifier
          schema:
            type: string
            example: device-demo-001
        - name: Authorization
          in: header
          required: true
          description: Bearer JWT
          schema:
            type: string
            example: >-
              Bearer
              eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJkZW1vLXVzZXIifQ.demo-signature
      responses:
        '200':
          description: Customer wallets retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponseCustomerWalletList'
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Customer not found
        '500':
          description: Internal server error
components:
  schemas:
    BaseResponseCustomerWalletList:
      type: object
      description: Standard API response wrapper with customer wallet list in data
      properties:
        code:
          type: integer
          format: int32
          examples:
            - 200
          description: HTTP-style status code
          example: 200
        data:
          type: array
          items:
            $ref: '#/components/schemas/CustomerWalletResponse'
          description: Customer wallets
        message:
          type: string
          examples:
            - Success
          description: Result message
          example: Success
    CustomerWalletResponse:
      type: object
      description: Customer wallet response payload
      properties:
        id:
          type: string
        walletId:
          type: string
        customerId:
          type: string
        name:
          type: string
        walletType:
          type: string
        status:
          type: string
        currency:
          type: string
        balance:
          type: string
        availableBalance:
          type: string
        iban:
          type: string

````