# Search Wallet

Searches for a wallet by currency code and optionally by network code. This endpoint must be called from your secure backend server.

If multiple networks exist for a currency and no network code is provided, the response will include available networks.

Security: Requires merchant authentication headers.

Endpoint: GET /wallets/search
Version: 1.0.0
Security: MerchantAuth

## Header parameters:

  - `merchant-client-id` (string, required)
    Your merchant client identifier (must be kept secure)

## Query parameters:

  - `currencyCode` (string, required)
    Currency code to search for
    Example: "USDT"

  - `networkCode` (string)
    Network code (required if currency supports multiple networks)
    Example: "ERC20"

## Response 200 fields (application/json):

  - `code` (string)
    Result code indicating the operation status
    Example: "OK"

  - `data` (object)
    Response data payload

  - `data.success` (boolean)
    Whether the lookup was successful
    Example: true

  - `data.message` (string)
    Result message
    Example: "Wallet found"

  - `data.wallet` (any)

  - `data.availableNetworks` (array)
    List of available networks for this currency
    Example: ["ERC20","TRC20","BEP20"]

  - `data.requiresNetworkCode` (boolean)
    Whether network code is required for this currency
    Example: true

  - `message` (string)
    Human-readable response message
    Example: "Operation completed successfully"

## Response 400 fields (application/json):

  - `code` (string)
    Error code
    Example: "INVALID_INPUT"

  - `message` (string)
    Error message
    Example: "Invalid JSON in request body"

## Response 401 fields (application/json):

  - `code` (string)
    Error code
    Example: "INVALID_INPUT"

  - `message` (string)
    Error message
    Example: "Invalid JSON in request body"

## Response 500 fields (application/json):

  - `code` (string)
    Error code
    Example: "INVALID_INPUT"

  - `message` (string)
    Error message
    Example: "Invalid JSON in request body"