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

# 查询未匹配的 Travel Rule 入账 API

> 通过 Didit 列出仍在等待来源 VASP 发送 Travel Rule 数据的入账记录，便于将每笔入账与对方发来的消息配对。



列出未匹配 Travel Rule 入金的 API 提示词
        将提示词复制到剪贴板



      
      

\<pre>

\`List the inbound deposits of my application that still wait for the originating VASP's Travel Rule data.

Endpoint:
GET https://verification.didit.me/v3/travel-rule/unmatched/

Authentication:
Use the x-api-key header with my Didit API key. A scoped API key needs the transactions privilege.

Which deposits it returns:
\- Inbound transfers whose status is AWAITING_COUNTERPARTY, NOT_ENOUGH_COUNTERPARTY_DATA or COUNTERPARTY_VASP_NOT_FOUND.
\- Only deposits with no received Travel Rule message paired to them and nobody matched by hand.

Query parameters (all optional): the same filters as GET /v3/travel-rule/transfers/ (direction, status, rail, kind, currency, start_date, end_date, counterparty), plus limit (default 50) and offset.

What to read from each row:
\- The same fields as a row of GET /v3/travel-rule/transfers/: id, transaction_id, txn_id, kind, direction, status, rail, asset, amount, originator_vasp, beneficiary_vasp, wallets, memos, matched_transaction_id, deadline_at, created_at.
\- transaction_id is the deposit to pass as {transaction_uuid} to POST /v3/travel-rule/unmatched/{transaction_uuid}/match/.

Failure modes:
\- 400 - a filter value is not valid, for example {"status": ["Unknown value(s): awaiting."]}.
\- 401 - invalid API key.
\- 403 - the key lacks the transactions privilege.

Full guide: /transaction-monitoring/travel-rule.`

\</pre>



      
      

粘贴到

## 何时使用入金可能会先到达你的钱包，而来源 VASP 的 Travel Rule 数据尚未到达 Didit。在数据到达之前，这笔入金会一直等待。
列出等待中的入金，找出需要处理的那些。当数据作为单独的接收消息到达时，请使用[匹配未匹配的入金](https://docs.didit.me/zh/management-api/travel-rule/match-unmatched-deposit.md)将两者配对。## 请求```bash theme={null}
curl "https://verification.didit.me/v3/travel-rule/unmatched/" \
  -H "x-api-key: YOUR_API_KEY"
```## 注意事项- 行和过滤器与[列出 Travel Rule 转账](https://docs.didit.me/zh/management-api/travel-rule/list-transfers.md)中的相同，按最新在前排序。
- 当收到的消息与入金配对、你手动匹配该入金，或入金状态发生变化时，该入金会从列表中移除。
- 对于没有 Travel Rule 转账的应用，列表为空。## 相关内容- [匹配未匹配的入金](https://docs.didit.me/zh/management-api/travel-rule/match-unmatched-deposit.md)
- [Travel Rule](https://docs.didit.me/zh/transaction-monitoring/travel-rule.md)


## OpenAPI

````yaml zh/openapi-25.json GET /v3/travel-rule/unmatched/
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/unmatched/:
    get:
      tags:
        - Travel Rule
      summary: 列出未匹配的 Travel Rule 充值
      description: >-
        仍在等待汇款方 VASP 的 Travel Rule 数据的入站充值：其转账状态为
        `AWAITING_COUNTERPARTY`、`NOT_ENOUGH_COUNTERPARTY_DATA` 或
        `COUNTERPARTY_VASP_NOT_FOUND`，未配对任何已接收的消息，且无人手动进行匹配。数据行和过滤器与 `GET
        /v3/travel-rule/transfers/` 相同，按最新优先排序，使用 `limit`（默认 50）和 `offset`
        进行分页。使用 `POST /v3/travel-rule/unmatched/{transaction_uuid}/match/`
        将充值与汇款方 VASP 发送的消息配对。
      operationId: listUnmatchedTravelRuleDeposits
      parameters:
        - name: direction
          in: query
          required: false
          schema:
            type: string
          description: INBOUND、OUTBOUND 或两者以逗号分隔。区分大小写。
        - name: status
          in: query
          required: false
          schema:
            type: string
          description: 一个或多个转账状态，以逗号分隔。
        - name: rail
          in: query
          required: false
          schema:
            type: string
          description: >-
            INTERNAL、TRP、GTR、TRUST、VERIFYVASP、SYGNA、EMAIL、TEST_VASP
            中的一个或多个，以逗号分隔。
        - name: kind
          in: query
          required: false
          schema:
            type: string
          description: withdrawal、deposit 或 message，以逗号分隔。
        - name: currency
          in: query
          required: false
          schema:
            type: string
          description: 交易的币种，不区分大小写。
        - name: start_date
          in: query
          required: false
          schema:
            type: string
            format: date
          description: 在此日期（UTC）或之后创建的转账，格式为 YYYY-MM-DD。
        - name: end_date
          in: query
          required: false
          schema:
            type: string
            format: date
          description: 在此日期（UTC）或之前创建的转账，格式为 YYYY-MM-DD。
        - name: counterparty
          in: query
          required: false
          schema:
            type: string
            format: uuid
          description: >-
            来自 GET /v3/travel-rule/vasps/ 的名录条目或 Didit 网络成员的
            `id`：用于获取您与该交易对手之间的转账。无效的 id 值将返回 400。
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            minimum: 1
            maximum: 1000000
          description: 页面大小，默认为 50。
        - name: offset
          in: query
          required: false
          schema:
            type: integer
            minimum: 0
            maximum: 1000000
          description: 要跳过的行。
      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/TravelRuleTransferRow'
              example:
                count: 1
                next: null
                previous: null
                results:
                  - id: 7d3a1c55-0b9e-4d52-8a3c-1f6e2b9d4a08
                    transaction_id: c41f9b2e-5a8d-4e0c-9f17-3b6d8a2e5c91
                    txn_id: dep-2026-10-20-0007
                    txn_date: '2026-10-19T08:41:12Z'
                    kind: deposit
                    direction: INBOUND
                    status: AWAITING_COUNTERPARTY
                    rail: TRP
                    asset: ETH
                    amount: '1.25'
                    originator_vasp: ''
                    beneficiary_vasp: Example Counterparty VASP
                    originator_wallet: '0x77ccff0cc624a53cd8b8d8703ced826710211ec7'
                    beneficiary_wallet: '0xede2d7e4f5b097e6391ab6bbcf2f47a53f4778cb'
                    originator_memo: ''
                    beneficiary_memo: ''
                    originator_wallet_type: vasp
                    beneficiary_wallet_type: vasp
                    matched_transaction_id: null
                    deadline_at: null
                    created_at: '2026-10-19T08:41:13Z'
        '400':
          description: 过滤器值无效。
          content:
            application/json:
              example:
                start_date:
                  - Use the YYYY-MM-DD format.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
      security:
        - ApiKeyAuth: []
      x-codeSamples:
        - lang: python
          label: Python
          source: |-
            from didit import Didit

            # Reads DIDIT_API_KEY.
            client = Didit()

            for item in client.travel_rule.unmatched_deposits.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.unmatchedDeposits.list())
            {
              console.log(item);
            }
        - lang: go
          label: Go
          source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\niter := client.TravelRule.UnmatchedDeposits.ListAutoPaging(ctx, didit.TravelRuleUnmatchedDepositsListParams{})\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().unmatchedDeposits().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->unmatchedDeposits->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.unmatched_deposits.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.UnmatchedDeposits.ListAsync())

            {
                Console.WriteLine(JsonSerializer.Serialize(item));
            }
components:
  schemas:
    TravelRuleTransferRow:
      type: object
      description: 转账列表中显示的一笔 Travel Rule 转账：仅包含 VASP 名称、钱包和备注，绝不包含汇款人或收款人的个人数据。
      properties:
        id:
          type: string
          format: uuid
          description: 转账的 id。
        transaction_id:
          type: string
          format: uuid
          description: 此转账所属的 Didit 交易。
        txn_id:
          type: string
          nullable: true
          description: 您为该交易指定的自身 ID。Didit 为您登记的转账（例如 Didit Test VASP 入账转账）将带有生成的 ID。
        txn_date:
          type: string
          format: date-time
        kind:
          type: string
          enum:
            - withdrawal
            - deposit
            - message
          description: >-
            withdrawal：出账。message：通道根据交易对手的消息创建的入账转账（TRP 查询、INTERNAL 入账分支，或
            GTR、VerifyVASP 或 Sygna Bridge 消息）。deposit：任何其他入账转账。
        direction:
          type: string
          enum:
            - INBOUND
            - OUTBOUND
        status:
          type: string
          enum:
            - AWAITING_COUNTERPARTY
            - ON_HOLD
            - COMPLETED
            - FINISHED
            - CANCELLED
            - EXPIRED
            - COUNTERPARTY_MISMATCHED_DATA
            - COUNTERPARTY_VASP_NOT_FOUND
            - COUNTERPARTY_VASP_NOT_REACHABLE
            - UNCONFIRMED_OWNERSHIP
            - COUNTERPARTY_VASP_GENERAL_DECLINE
            - NOT_ENOUGH_COUNTERPARTY_DATA
            - NOT_APPLICABLE
        reason:
          type: string
          description: >-
            `COUNTERPARTY_VASP_NOT_FOUND` 或 `COUNTERPARTY_VASP_NOT_REACHABLE`
            转账受阻的原因，取值与转账自身的 `reason`
            相同，因此列表无需逐一打开每笔转账即可区分合规邮件退信与无路由的交易对手。任何其他状态下为
            `""`。参见[转账受阻的原因](/zh/transaction-monitoring/travel-rule#为什么转账会卡住)。
        rail:
          type: string
          nullable: true
          enum:
            - INTERNAL
            - TRP
            - GTR
            - TRUST
            - VERIFYVASP
            - SYGNA
            - EMAIL
            - TEST_VASP
            - null
        asset:
          type: string
          description: 交易的币种。
        amount:
          type: string
          description: 普通小数形式的金额，例如 "1.25"。
        originator_vasp:
          type: string
          description: >-
            出向：您 VASP 的法定名称。入向：交易对手的名称，来自其目录条目、Didit 网络成员、TRP 发送方、Didit Test
            VASP 或转账声明的名称。未知时为空。
        beneficiary_vasp:
          type: string
          description: 出向：以相同方式计算得出的交易对手名称。入向：您 VASP 的法定名称。
        originator_wallet:
          type: string
        beneficiary_wallet:
          type: string
        originator_memo:
          type: string
          description: Memo 或目标标签，在没有该项的链上为空。
        beneficiary_memo:
          type: string
        originator_wallet_type:
          type: string
          enum:
            - vasp
            - self_hosted
            - own
          description: vasp、self_hosted（声明为非托管）或 own（您的地址簿中记录为属于您的钱包）。您自己的一方始终为 vasp。
        beneficiary_wallet_type:
          type: string
          enum:
            - vasp
            - self_hosted
            - own
        matched_transaction_id:
          type: string
          format: uuid
          nullable: true
          description: 您手动与已声明转账相匹配的充值交易另一方。
        deadline_at:
          type: string
          format: date-time
          nullable: true
          description: >-
            如果转账仍在等待其交易对手，该转账过期的时间。针对您使用 `POST /v3/transactions/`
            创建且需要进行交换的出账或入账的每一笔转账进行设置。低于阈值、不适用 Travel Rule 的闪电网络支付，以及交易对手联系到您时
            Didit 创建的入账转账（入账 TRP 问询、网络消息或 INTERNAL 入账环节）时为 null。
        created_at:
          type: string
          format: date-time
  responses:
    Unauthorized:
      description: 未授权
      content:
        application/json:
          examples:
            Invalid API Key:
              summary: 无效的 API 密钥
              value:
                detail: Invalid API Key.
    Forbidden:
      description: 禁止访问
      content:
        application/json:
          examples:
            No Permission:
              summary: 无权限
              value:
                detail: You do not have permission to perform this action.
            Not Enough Credits:
              summary: 额度不足
              value:
                error: >-
                  You don't have enough credits to perform this request. Please
                  top up at https://business.didit.me
  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.