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

# List Addresses

> Retrieve all blockchain addresses for a specific subwallet

<Note>
  **Auth method: Signed (HMAC)** — this endpoint requires the full set of signed
  headers: `x-access-id`, `x-request-id`, `x-timestamp`, and an HMAC-SHA256
  `authorization` signature. See [Authentication](/api-reference/authentication#signed-hmac-authentication).
</Note>

## Example

<CodeGroup>
  ```javascript Node.js theme={null}
  const res = await fetch(`${BASE}/wallet/user-8821/addresses?page=1&limit=20`, {
    headers: makeHeaders(),
  });

  const { data } = await res.json();
  /*
  [
    { network: 'ethereum', address: '0xabc...', address_reference: 'ref-1' },
    { network: 'polygon',  address: '0xdef...', address_reference: 'ref-1' }
  ]
  */
  ```

  ```python Python theme={null}
  res = requests.get(
      f"{BASE}/wallet/user-8821/addresses",
      headers=make_headers(),
      params={"page": 1, "limit": 20},
  )
  addresses = res.json()["data"]
  ```
</CodeGroup>

## Headers

<ParamField header="authorization" type="string" required>
  Base64-encoded HMAC-SHA256 signature of the request payload using the API secret

  **Example:** `"5e73d044c44d733fcf819ad3409aaad..."`
</ParamField>

<ParamField header="x-timestamp" type="string" required>
  Current timestamp in ISO 8601 format

  **Example:** `"2025-03-15T09:45:53.000Z"`
</ParamField>

<ParamField header="x-request-id" type="string" required>
  Unique identifier for the request (UUID v4)

  **Example:** `"550e8400-e29b-41d4-a716-446655440000"`
</ParamField>

<ParamField header="x-access-id" type="string" required>
  Your API access ID provided by Tender

  **Example:** `"your-access-id-here"`
</ParamField>

## Path Parameters

<ParamField path="walletReference" type="string" required>
  The reference of the wallet whose addresses you want to list.

  **Example:** `"user-8821"`
</ParamField>

## Query Parameters

<ParamField query="page" type="number">
  Page number for pagination. Defaults to `1`.

  **Example:** `1`
</ParamField>

<ParamField query="limit" type="number">
  Number of addresses per page. Defaults to `20`.

  **Example:** `20`
</ParamField>

## Response

<ResponseField name="status" type="string" required>
  **Example:** `"success"`
</ResponseField>

<ResponseField name="message" type="string" required>
  **Example:** `"success"`
</ResponseField>

<ResponseField name="data" type="array" required>
  List of address objects.

  <Expandable title="address object">
    <ResponseField name="network" type="string">
      The blockchain network.

      **Example:** `"ethereum"`
    </ResponseField>

    <ResponseField name="address" type="string">
      The blockchain address.

      **Example:** `"0xabc123..."`
    </ResponseField>

    <ResponseField name="address_reference" type="string">
      The label assigned to this address slot.

      **Example:** `"ref-1"`
    </ResponseField>
  </Expandable>
</ResponseField>


## OpenAPI

````yaml GET /v1/api/wallet/{walletReference}/addresses
openapi: 3.1.0
info:
  title: Tender API
  description: Tender Developer API for cryptocurrency payments and agent management
  version: 1.0.0
  contact:
    name: Tender Support
    url: https://tender.cash
servers:
  - url: https://secureapi.tender.cash
    description: Production Server
  - url: https://sandbox-api.tender.cash
    description: Sandbox Server
security:
  - SignedAuth: []
tags:
  - name: Agents
    description: Manage agents and sub-businesses
  - name: Transactions
    description: Payment and transaction operations
  - name: System
    description: System information and configuration
  - name: Webhooks
    description: Webhook management and logs
  - name: On-ramp
    description: Fiat-to-crypto on-ramp operations
  - name: Payouts
    description: Send crypto from merchant balance to a wallet address or payout account
  - name: Subwallets
    description: Provision and manage crypto wallet infrastructure for your end-users
paths:
  /v1/api/wallet/{walletReference}/addresses:
    get:
      tags:
        - Subwallets
      summary: List Addresses
      description: Retrieve all blockchain addresses for a specific subwallet.
      operationId: listSubWalletAddresses
      parameters:
        - name: walletReference
          in: path
          required: true
          schema:
            type: string
          example: user-8821
        - name: authorization
          in: header
          required: true
          schema:
            type: string
        - name: x-timestamp
          in: header
          required: true
          schema:
            type: string
            format: date-time
          example: '2025-03-15T09:45:53.000Z'
        - name: x-request-id
          in: header
          required: true
          schema:
            type: string
            format: uuid
          example: 550e8400-e29b-41d4-a716-446655440000
        - name: x-access-id
          in: header
          required: true
          schema:
            type: string
          example: your-access-id-here
        - name: page
          in: query
          schema:
            type: integer
            default: 1
        - name: limit
          in: query
          schema:
            type: integer
            default: 20
      responses:
        '200':
          description: List of addresses
          content:
            application/json:
              example:
                status: success
                message: success
                data:
                  - network: ethereum
                    address: 0xabc123...
                    address_reference: ref-1
                  - network: polygon
                    address: 0xdef456...
                    address_reference: ref-1
      security:
        - SignedAuth: []
components:
  securitySchemes:
    SignedAuth:
      type: apiKey
      in: header
      name: authorization
      description: >-
        Signed (HMAC) authentication. Required headers: x-access-id,
        x-request-id (UUID v4), x-timestamp (ISO 8601), and authorization
        (Base64 HMAC-SHA256 signature of {timeStamp, requestId, accessId} using
        your access secret).

````