> ## 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 管理 API，向 Travel Rule 转账的交易对手 VASP 发送消息或证件请求，并可附带附件。 发送 Travel Rule 消息 API 提示词 将提示词复制到剪贴板 \

\`Send a message or a document request to the counterparty VASP of a Travel Rule transfer, so a disputed transfer is resolved inside Didit.

Endpoint:
POST https://verification.didit.me/v3/transactions/{transaction_id}/travel-rule/messages/

Authentication:
Use the x-api-key header with my Didit API key. {transaction_id} is the Didit transaction uuid on my application.

Request body (JSON, or multipart/form-data when attaching files):
\- kind - MESSAGE (default) or DOCUMENT_REQUEST.
\- body - up to 5000 characters. A MESSAGE needs a body or a file.
\- requested_documents - up to 10 names. A DOCUMENT_REQUEST needs at least one; a MESSAGE must not have any.
\- reply_to - uuid of an earlier message of the same transfer. A reply carrying a document fulfils the request it answers.
\- files - multipart only, up to 5 files of 10 MB each.

Example call:
curl -X POST "https://verification.didit.me/v3/transactions/{transaction_id}/travel-rule/messages/" \
-H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"kind": "DOCUMENT_REQUEST", "body": "Please confirm the beneficiary date of birth.", "requested_documents": ["Proof of address"]}'

Behavior:
\- Works on INTERNAL transfers (the other Didit customer sees it on its side) and EMAIL transfers (the counterparty is emailed and answers in the pickup portal).
\- A transfer holds up to 100 messages.

Failure modes:
\- 400 - invalid body, file rejected, 100 messages reached, or reply_to is not a message of this transfer.
\- 404 - unknown transaction, or no Travel Rule transfer on it.
\- 409 - no message can reach the counterparty; detail gives the reason: a network rail (TRP, GTR, TRUST, VerifyVASP, Sygna) carries no messages, no counterparty yet, an INTERNAL transfer whose data did not match the wallet holder, an INTERNAL transfer whose recipient has not proved control of the wallet yet, an EMAIL transfer whose counterparty no longer has a compliance email address, or an EMAIL transfer whose pickup link expired or whose transfer is closed.

Full guide: /transaction-monitoring/travel-rule#messages-and-document-requests.`

\
粘贴到 ## OpenAPI ````yaml zh/openapi-25.json POST /v3/transactions/{transaction_id}/travel-rule/messages/ 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/transactions/{transaction_id}/travel-rule/messages/: post: tags: - Travel Rule summary: 发送 Travel Rule 消息或证件请求 description: >- 向交易对手 VASP 发送消息或证件请求。适用于 INTERNAL 转账（另一位 Didit 客户会在其配对端看到）和 EMAIL 转账（通过电子邮件通知交易对手，交易对手在提取门户中回复）。通过 TRP、GTR、TRUST、VerifyVASP 或 Sygna 进行的转账不携带任何消息，因为这些协议不支持消息。限制：每次转账最多 100 条消息，正文最多 5000 个字符，最多 10 份请求的证件，最多 5 个文件（每个 10 MB）。 operationId: createTravelRuleMessage parameters: - name: transaction_id in: path required: true description: 拥有该转账的 Didit 稳定交易 UUID。 schema: type: string format: uuid requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/TravelRuleMessageCreateRequest' example: kind: DOCUMENT_REQUEST body: Please confirm the date of birth of the beneficiary. requested_documents: - Proof of address multipart/form-data: schema: $ref: '#/components/schemas/TravelRuleMessageCreateRequest' responses: '201': description: 存储的消息。 content: application/json: schema: $ref: '#/components/schemas/TravelRuleMessage' '400': description: 无效的请求体、不被接受的文件类型或大小、该笔转账上的消息已超过 100 条，或者 `reply_to` 不是该笔转账的消息。 content: application/json: schema: type: object example: requested_documents: - Name at least one document the counterparty should send. '404': description: 未知的交易或 token，或者该交易没有 Travel Rule 转账。 '409': description: >- 没有任何消息可以送达交易对手。`detail` 说明了原因：转账通过网络通道（TRP、GTR、TRUST、VerifyVASP 或 Sygna）进行；尚无交易对手；INTERNAL 转账的数据与钱包持有人不匹配导致未向接收方发送任何内容；或者 EMAIL 转账的提取链接已过期或转账已关闭。 content: application/json: schema: type: object properties: detail: type: string security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X POST https://verification.didit.me/v3/transactions/{transaction_id}/travel-rule/messages/ \ -H 'x-api-key: YOUR_API_KEY' -H 'Content-Type: application/json' \ -d '{"kind": "DOCUMENT_REQUEST", "body": "Please confirm the date of birth of the beneficiary.", "requested_documents": ["Proof of address"]}' - lang: python label: Python source: |- from didit import Didit # Reads DIDIT_API_KEY. client = Didit() result = client.transactions.travel_rule.create_message( "11111111-2222-3333-4444-555555555555", kind="DOCUMENT_REQUEST", body="Please confirm the date of birth of the beneficiary.", requested_documents=["Proof of address"], ) print(result) - lang: javascript label: Node.js source: >- import Didit from "@didit-protocol/sdk-node"; // Reads DIDIT_API_KEY. const didit = new Didit(); const result = await didit.transactions.travelRule.createMessage("11111111-2222-3333-4444-555555555555", { kind: "DOCUMENT_REQUEST", body: "Please confirm the date of birth of the beneficiary.", requested_documents: ["Proof of address"], }); console.log(result); - lang: go label: Go source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\nresult, err := client.Transactions.TravelRule.CreateMessage(ctx, \"11111111-2222-3333-4444-555555555555\", didit.TravelRuleMessageCreateRequest{\n\tKind: didit.Some(didit.TravelRuleMessageCreateRequestKind(\"DOCUMENT_REQUEST\")),\n\tBody: didit.String(\"Please confirm the date of birth of the beneficiary.\"),\n\tRequestedDocuments: didit.Some([]string{\"Proof of address\"}),\n})\nif err != nil {\n\tlog.Fatal(err)\n}\nfmt.Printf(\"%+v\\n\", result)" - lang: java label: Java source: >- import java.util.List; import me.didit.Didit; import me.didit.types.TravelRuleMessageCreateRequest; // Reads DIDIT_API_KEY. Didit client = new Didit(); var result = client.transactions().travelRule().createMessage("11111111-2222-3333-4444-555555555555", TravelRuleMessageCreateRequest.builder() .kind(TravelRuleMessageCreateRequest.Kind.of("DOCUMENT_REQUEST")) .body("Please confirm the date of birth of the beneficiary.") .requestedDocuments(List.of("Proof of address")) .build()); System.out.println(result); - lang: php label: PHP source: >- transactions->travelRule->createMessage('11111111-2222-3333-4444-555555555555', [ 'kind' => 'DOCUMENT_REQUEST', 'body' => 'Please confirm the date of birth of the beneficiary.', 'requested_documents' => ['Proof of address'], ]); print_r($result->toArray()); - lang: ruby label: Ruby source: |- require "didit" # Reads DIDIT_API_KEY. didit = Didit::Client.new result = didit.transactions.travel_rule.create_message( "11111111-2222-3333-4444-555555555555", kind: "DOCUMENT_REQUEST", body: "Please confirm the date of birth of the beneficiary.", requested_documents: ["Proof of address"] ) puts result.to_h - lang: csharp label: .NET source: >- using System; using System.Text.Json; using Didit; // Reads DIDIT_API_KEY. using var client = new DiditClient(); var result = await client.Transactions.TravelRule.CreateMessageAsync("11111111-2222-3333-4444-555555555555", new TravelRuleMessageCreateRequest { Kind = new TravelRuleMessageCreateRequestKind("DOCUMENT_REQUEST"), Body = "Please confirm the date of birth of the beneficiary.", RequestedDocuments = new string[] { "Proof of address" }, }); Console.WriteLine(JsonSerializer.Serialize(result)); components: schemas: TravelRuleMessageCreateRequest: type: object description: 以 JSON 格式发送，或以 multipart/form-data 格式发送并将附件放入 `files` 中。 properties: kind: type: string enum: - MESSAGE - DOCUMENT_REQUEST default: MESSAGE body: type: string maxLength: 5000 description: MESSAGE 所必需，除非附加了文件。 requested_documents: type: array items: type: string maxLength: 255 maxItems: 10 description: DOCUMENT_REQUEST 所必需（至少一个），且仅允许在该类型中使用。 reply_to: type: string format: uuid nullable: true description: 同一笔转账的消息。携带证件的回复可满足其所响应的证件请求。 files: type: array items: type: string format: binary maxItems: 5 description: 仅限 multipart。最多 5 个文件，每个文件不超过 10 MB。 TravelRuleMessage: type: object properties: id: type: string format: uuid kind: type: string enum: - MESSAGE - DOCUMENT_REQUEST direction: type: string enum: - INBOUND - OUTBOUND description: '`OUTBOUND` 是读取方自身发送的内容。在 pickup 门户中，方向是来自交易对手一方。' author: type: string description: 在其所属方写入该内容的主体：控制台用户的邮箱、API 密钥标签，或对方 VASP 的名称。 body: type: string requested_documents: type: array items: type: string description: DOCUMENT_REQUEST 所请求的内容，以请求者的措辞描述。 reply_to: type: string format: uuid nullable: true fulfilled_at: type: string format: date-time nullable: true description: 一旦对 DOCUMENT_REQUEST 的回复携带了证件，便会在该请求上设置。 attachment: $ref: '#/components/schemas/TravelRuleMessageAttachment' created_at: type: string format: date-time TravelRuleMessageAttachment: type: object nullable: true description: 附加到消息的证件，像任何其他交易证件一样存储。 properties: uuid: type: string format: uuid label: type: string nullable: true note: type: string nullable: true uploaded_by: type: string nullable: true description: 附加该文件的主体。在提取门户中，您发送的文件会显示您的 VASP 名称，绝不会显示其背后的个人或 API 密钥。 created_at: type: string format: date-time files: type: array items: type: object properties: uuid: type: string format: uuid file_url: type: string nullable: true description: 有时限的下载 URL。 original_filename: type: string file_size: type: integer 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.