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

# 钱包地址列表 API：Travel Rule 地址簿

> Didit 提供列出钱包地址簿条目的接口。入站 INTERNAL 通道的 Travel Rule 转账据此解析地址，并附带所有权验证状态。

列出钱包地址 API 提示词
将提示词复制到剪贴板

<pre>
  \`List the application's Travel Rule wallet address book - the registry of wallets you control that inbound INTERNAL-rail transfers resolve against.

  Endpoint:
  GET [https://verification.didit.me/v3/travel-rule/wallet-addresses/](https://verification.didit.me/v3/travel-rule/wallet-addresses/)

  Authentication:
  Use the x-api-key header with my Didit API key.

  Query parameters:

  * limit / offset - pagination; count/next/previous describe the page window.

  What to read from each entry:

  * uuid - the entry id, used in PATCH/DELETE /v3/travel-rule/wallet-addresses/{entry_uuid}/.
  * address, chain - the registered wallet.
    When a transfer names a chain, sunrise registration, the INTERNAL rail and the outbound TRP travel-address lookup match an entry only when its chain equals the transfer's chain (case-insensitive) or the entry's chain is blank.
    Chain names are not translated, so an entry with chain "ethereum" does not match a transfer with chain "ETH".
    Inbound TRP inquiries and ownership confirmation ignore the chain and match by address (an inbound TRP inquiry that carries no address matches a verified entry by holder\_name instead).
  * holder\_name / holder\_vendor\_data / entity\_type - the wallet holder, used for the beneficiary name match.
  * travel\_address - the counterparty VASP's travel address for this wallet, when known; it lets outbound transfers of an asset TRP carries (BTC, ETH, and USDC on a named network) to this wallet route over TRP.
  * is\_ownership\_verified - whether control of this address has been proven (wallet-ownership widget or self-declaration). Verified entries let inbound transfers skip UNCONFIRMED\_OWNERSHIP.

  Full guide: /transaction-monitoring/travel-rule#wallet-address-book.\`
</pre>

粘贴到


## OpenAPI

````yaml zh/openapi-25.json GET /v3/travel-rule/wallet-addresses/
openapi: 3.0.0
info:
  version: 3.0.0
  title: Didit Verification API
  description: 身份证件验证 API。使用 x-api-key 请求头进行身份验证。
servers:
  - url: https://verification.didit.me
security: []
tags: []
paths:
  /v3/travel-rule/wallet-addresses/:
    get:
      tags:
        - Travel Rule
      summary: 列出钱包地址簿条目
      description: 您应用的 Travel Rule 钱包地址簿分页列表，最新优先。
      operationId: listTravelRuleWalletAddresses
      parameters:
        - name: limit
          in: query
          schema:
            type: integer
            default: 50
            minimum: 1
        - name: offset
          in: query
          schema:
            type: integer
            default: 0
            minimum: 0
      responses:
        '200':
          description: 分页钱包地址簿条目。
          content:
            application/json:
              schema:
                type: object
                properties:
                  count:
                    type: integer
                  next:
                    type: string
                    nullable: true
                  previous:
                    type: string
                    nullable: true
                  results:
                    type: array
                    items:
                      $ref: '#/components/schemas/WalletAddressEntry'
      security:
        - ApiKeyAuth: []
      x-codeSamples:
        - lang: curl
          label: curl
          source: >-
            curl -X GET
            https://verification.didit.me/v3/travel-rule/wallet-addresses/ \
              -H 'x-api-key: YOUR_API_KEY'
        - lang: python
          label: Python
          source: |-
            from didit import Didit

            # Reads DIDIT_API_KEY.
            client = Didit()

            for item in client.travel_rule.wallet_addresses.list():
                print(item)
        - lang: javascript
          label: Node.js
          source: |-
            import Didit from "@didit-protocol/sdk-node";

            // Reads DIDIT_API_KEY.
            const didit = new Didit();

            for await (const item of didit.travelRule.walletAddresses.list()) {
              console.log(item);
            }
        - lang: go
          label: Go
          source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\niter := client.TravelRule.WalletAddresses.ListAutoPaging(ctx, didit.TravelRuleWalletAddressesListParams{})\nfor iter.Next() {\n\tfmt.Printf(\"%+v\\n\", iter.Current())\n}\nif err := iter.Err(); err != nil {\n\tlog.Fatal(err)\n}"
        - lang: java
          label: Java
          source: |-
            import me.didit.Didit;

            // Reads DIDIT_API_KEY.
            Didit client = new Didit();

            for (var item : client.travelRule().walletAddresses().list()) {
                System.out.println(item);
            }
        - lang: php
          label: PHP
          source: |-
            <?php

            require 'vendor/autoload.php';

            use Didit\DiditClient;

            // Reads DIDIT_API_KEY.
            $didit = new DiditClient();

            foreach ($didit->travelRule->walletAddresses->list() as $item) {
                print_r($item->toArray());
            }
        - lang: ruby
          label: Ruby
          source: |-
            require "didit"

            # Reads DIDIT_API_KEY.
            didit = Didit::Client.new

            didit.travel_rule.wallet_addresses.list.auto_paging_each do |item|
              puts item.to_h
            end
        - lang: csharp
          label: .NET
          source: >-
            using System;

            using System.Text.Json;

            using Didit;


            // Reads DIDIT_API_KEY.

            using var client = new DiditClient();


            await foreach (var item in await
            client.TravelRule.WalletAddresses.ListAsync())

            {
                Console.WriteLine(JsonSerializer.Serialize(item));
            }
components:
  schemas:
    WalletAddressEntry:
      type: object
      properties:
        uuid:
          type: string
          format: uuid
        address:
          type: string
          description: >-
            钱包地址；仅通过哈希导入的条目为 `""`。在每个应用、链和 memo
            维度内唯一，比对地址时不区分大小写。删除条目后，您可以再次注册相同的地址。
        chain:
          type: string
          description: >-
            地址的区块链网络 token，例如 `ETH` 或 `BTC`。当 Didit
            路由或登记转账时，它会按钱包地址进行地址簿条目匹配；如果转账包含区块链网络，还会对此值进行不区分大小写的匹配。转账的区块链网络为
            `beneficiary_data.chain`，如果您未发送，则从交易的加密区块链网络或货币符号（例如
            `ETH`）中填充，或是存款后登记的 `chain`，因此请在所有地方使用相同的
            token。区块链网络为空的条目可匹配任意网络。在比特币上登记的 Lightning 收款人（节点 ID 或 Lightning
            Address）以小写形式存储在 `LIGHTNING` 下，并在该处匹配 Lightning
            转账。无论您发送何种拼写，已知区块链网络均存储在同一个标准标识符下："ethereum"、"Ethereum" 和 "ERC20"
            均存储为 ETH，"BNB Smart Chain" 和 "BEP20" 存储为 BNB，"tron" 存储为
            TRX。未知区块链网络名称将按原样保留。
        holder_vendor_data:
          type: string
          description: 您为持有者指定的内部标识符。
        holder_name:
          type: string
          description: 钱包持有者姓名，用于收款人姓名比对。
        entity_type:
          type: string
          description: 自由格式文本，默认为 "individual"。
        is_ownership_verified:
          type: boolean
          description: 只读。此地址的所有权是否已得到证明。
        created_at:
          type: string
          format: date-time
        travel_address:
          type: string
          description: >-
            此钱包对应的交易对手 VASP 的 Travel Address（如果已知）。允许 Didit 针对 TRP 支持的资产（指定网络上的
            BTC、ETH 和 USDC），通过 TRP 渠道路由此收款人的转账。
        address_hash:
          type: string
          description: 只读。小写地址的 SHA-256，为小写十六进制格式。仅通过哈希导入的条目将基于此进行匹配。
        memo:
          type: string
          description: >-
            在 memo 网络（XRP、XLM、EOS、ATOM、HBAR）上作为钱包一部分的目标标签或 memo；整个地址为 `""`。带有
            memo 的条目仅匹配指定该 memo 的转账；不带 memo 的条目匹配整个地址。
        receiving_travel_address:
          type: string
          readOnly: true
          description: >-
            此钱包专属的 Travel Address：将其提供给发送方 VASP，以便其 TRP 查询能够指定此钱包。如果钱包被记录为另一个
            VASP 的钱包、Travel Rule 未启用或在您的 VASP 资料保存之前，此字段为空。
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        您的应用 API 密钥，可在 Business Console 的“开发者 -> API
        密钥”中获取。主密钥拥有完整访问权限。指定名称的密钥可设置作用域：针对每个资源设为无权限、只读或读写，限定于特定工作流或已通过的会话、限定于
        IP 地址列表，以及设置到期日期。401 表示密钥错误、已撤销或已过期；403 表示未发送密钥、密钥无权访问该资源或操作，或请求来自其 IP
        列表之外的地址；在会话路由上返回 404 表示该会话不在该密钥允许的工作流或状态范围内。没有媒体访问权限的密钥获取到的图片、视频和 PDF
        URL 将为 null；没有会话写入权限的密钥获取到的会话链接和 token 将为 null。请参阅
        https://docs.didit.me/console/api-keys。

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.