> ## 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. # 交易 PDF 报告 API > 通过 Didit 下载受监控交易的 PDF 报告，包含判定结果、交易双方、警报、规则运行、筛查结果及关联交易。 生成交易 PDF 报告 API 提示词 将提示词复制到剪贴板 \

\`Download one Didit monitored transaction as a PDF report through the Management API.

Endpoint:
GET https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/transactions/{transaction_uuid}/pdf/

Authentication:
Use the x-api-key header with my Didit API key. A scoped key needs media: read and transactions: read, because a PDF report counts as media. Keys limited to specific workflows or to approved sessions cannot call this endpoint.

Goal:
\- Get a PDF of a transaction for an audit file, a handoff to another team, or a regulator request.

Path parameters:
\- organization_id: my organization UUID.
\- application_id: the UUID of the application my API key belongs to. Any other application returns 403.
\- transaction_uuid: the Didit transaction uuid, not my own txn_id.

Behavior:
\- The response body is the PDF itself (Content-Type: application/pdf). Do not parse it as JSON.
\- Content-Disposition is always attachment; filename=transaction_{transaction_uuid}.pdf.
\- The report covers the overview and verdict, parties and payment methods, custom properties, alerts and rule runs, screening and Travel Rule results, the network summary, the cost breakdown, up to 50 related transactions and the 20 most recent activity entries.
\- It is rendered from the transaction's current data on every call. Nothing is stored and nothing is billed. Rendering can take a few seconds, so use a generous client timeout.

Example call:
curl -X GET "https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/transactions/{transaction_uuid}/pdf/" \
-H "x-api-key: YOUR_API_KEY" \
-o transaction_report.pdf

Failure modes (JSON bodies):
\- 401: the API key has expired.
\- 403: missing API key (a wrong, revoked or expired key gets 401) ({"detail": "Authentication credentials were not provided or are invalid."}), an application_id that is not my key's application ({"detail": "You do not have permission to perform this action."}), a scoped key without media: read ({"detail": "This API key has no read access to media."}) or transactions: read, a key with workflow or status limits, or a request from outside the key's IP allowlist.
\- 404: no transaction with this uuid in my application ({"detail": "No Transaction matches the given query."}).
\- 429: more than 600 GET requests per minute with this key; wait Retry-After seconds and retry.

Side effects: none.

For the full integration shape, see /integration/integration-prompt.`

\
粘贴到 报告会根据交易的当前数据按需生成，因此在状态变更后需要再次调用，才能获取最新副本。与其他交易端点不同，它使用应用级路径：请在 URL 中填入您的组织 ID，以及 API 密钥所属应用的 ID。参见[查找您的组织 ID](https://docs.didit.me/zh/getting-started/api-authentication.md#获取您的组织-id)。> [!NOTE] > > PDF 报告属于媒体内容。[限定范围的 API 密钥](https://docs.didit.me/zh/console/api-keys.md)需要 **media: read** 和 **transactions: read** 两项权限。没有媒体访问权限的密钥即使能通过[获取交易](https://docs.didit.me/zh/management-api/transactions/get.md)以 JSON 形式读取交易，也会收到 `403`。 ## OpenAPI ````yaml zh/openapi-25.json GET /v3/organization/{organization_id}/application/{application_id}/transactions/{transaction_uuid}/pdf/ 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/organization/{organization_id}/application/{application_id}/transactions/{transaction_uuid}/pdf/: get: tags: - Transactions summary: 下载交易 PDF 报告 description: >- 将一笔被监控的交易渲染为 PDF 报告：概览与结论、当事方与支付方式、自定义属性、警报与规则运行情况、筛查与 Travel Rule 结果、网络摘要、费用明细、最多 50 笔相关交易以及最近 20 条活动条目。响应体为 PDF 本身（`application/pdf`），而非 JSON。 报告在每次调用时均根据交易的当前数据进行渲染，因此在状态更改后请重新请求。不会存储任何内容，也不会计费。渲染可能需要几秒钟，因此请设置宽松的客户端超时时间。 该 endpoint 位于应用作用域路径下：在 URL 中填入您的组织 ID 以及您的 API 密钥所属的应用 ID（[查找您的组织 ID](https://docs.didit.me/zh/getting-started/api-authentication#获取您的组织-id)）。PDF 报告算作媒体资源：有作用域限制的 API 密钥需要 `media: read` 和 `transactions: read` 权限，且仅限于某些工作流或已通过会话的密钥无法调用该接口。 operationId: get_transaction_pdf parameters: - name: organization_id in: path required: true schema: type: string format: uuid description: 组织 UUID。 example: 11111111-2222-3333-4444-555555555555 - name: application_id in: path required: true schema: type: string format: uuid description: 应用 UUID。必须是该 API 密钥所属的应用：在任何其他应用上使用该密钥都会返回 `403`。 example: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee - name: transaction_uuid in: path required: true description: >- Didit 交易 UUID：由 `POST /v3/transactions/` 和 `GET /v3/transactions/` 返回的 `uuid`。不接受您自己的 `txn_id`。 schema: type: string format: uuid example: abcdef12-3456-7890-abcd-ef1234567890 responses: '200': description: 渲染生成的 PDF，直接以二进制 `application/pdf` 形式返回。 headers: Content-Disposition: description: 始终为 `attachment; filename=transaction_{transaction_uuid}.pdf`。 schema: type: string example: >- attachment; filename=transaction_abcdef12-3456-7890-abcd-ef1234567890.pdf content: application/pdf: schema: type: string format: binary '401': description: API 密钥已过期。仅创建时设置了到期日期的密钥才会过期；超过该日期后，使用它的每次请求都会返回 `401`。 content: application/json: schema: type: object properties: detail: type: string examples: Expired key: value: detail: This API key has expired. '403': description: >- 该请求不被允许。请查看 `detail`：缺失 API 密钥（错误、已撤销或已过期的密钥会收到 `401`）、非该密钥所属应用的 `application_id`、缺少 `media: read` 或 `transactions: read` 的限定作用域密钥、受限于工作流或已通过的会话的密钥，或来自密钥 IP 列表之外的请求。 content: application/json: schema: type: object properties: detail: type: string examples: Missing or invalid key: value: detail: >- Authentication credentials were not provided or are invalid. Another application: value: detail: You do not have permission to perform this action. Scoped key without media read: value: detail: This API key has no read access to media. Scoped key without transactions read: value: detail: This API key has no read access to transactions. Key limited to workflows or approved sessions: value: detail: >- This API key only reaches sessions inside its workflow or status limits, so it can't use this endpoint. Outside the key's IP list: value: detail: This API key can't be used from this IP address. '404': description: >- 应用中不存在具有此 UUID 的交易（从未创建、已删除或属于另一个应用）。非 UUID 格式的 `transaction_uuid` 不会到达 API：它将返回 `404` HTML 页面，而不是此 JSON 正文。 content: application/json: schema: type: object properties: detail: type: string examples: Not found: value: detail: No Transaction matches the given query. '429': description: 使用此 API 密钥的 GET 请求每分钟超过 600 次。请等待 `Retry-After` 中指定的秒数，然后再重试。 content: application/json: schema: type: object properties: detail: type: string examples: Throttled: value: detail: >- GET request rate limit exceeded. You can make up to 600 requests per minute. headers: Retry-After: description: 距离当前一分钟窗口重置的秒数。 schema: type: integer example: 23 X-RateLimit-Limit: description: 在此预算中每分钟允许的请求数。 schema: type: integer X-RateLimit-Remaining: description: 当前时间窗口内剩余的请求数。 schema: type: integer X-RateLimit-Reset: description: 窗口重置的 Unix 时间。 schema: type: integer security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl --fail -X GET 'https://verification.didit.me/v3/organization/11111111-2222-3333-4444-555555555555/application/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/transactions/abcdef12-3456-7890-abcd-ef1234567890/pdf/' \ -H 'x-api-key: YOUR_API_KEY' \ --output transaction_report.pdf - lang: python label: Python source: |- from didit import Didit # Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID # and DIDIT_APPLICATION_ID. client = Didit() content = client.transactions.generate_pdf( "abcdef12-3456-7890-abcd-ef1234567890", ) with open("download.pdf", "wb") as file: file.write(content) - lang: javascript label: Node.js source: >- import { writeFile } from "node:fs/promises"; import Didit from "@didit-protocol/sdk-node"; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. const didit = new Didit(); const content = await didit.transactions.generatePdf("abcdef12-3456-7890-abcd-ef1234567890"); await writeFile("download.pdf", Buffer.from(await content.arrayBuffer())); - lang: go label: Go source: "ctx := context.Background()\n// Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID\n// and DIDIT_APPLICATION_ID.\nclient := didit.NewClient()\n\nresp, err := client.Transactions.GeneratePDF(ctx, \"abcdef12-3456-7890-abcd-ef1234567890\")\nif err != nil {\n\tlog.Fatal(err)\n}\ndefer resp.Body.Close()\nfile, err := os.Create(\"download.pdf\")\nif err != nil {\n\tlog.Fatal(err)\n}\ndefer file.Close()\nif _, err := io.Copy(file, resp.Body); err != nil {\n\tlog.Fatal(err)\n}" - lang: java label: Java source: >- import java.nio.file.Path; import me.didit.Didit; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. Didit client = new Didit(); client.transactions().generatePdf("abcdef12-3456-7890-abcd-ef1234567890") .writeTo(Path.of("download.pdf")); - lang: php label: PHP source: >- transactions->generatePdf('abcdef12-3456-7890-abcd-ef1234567890'); $content->saveTo('download.pdf'); - lang: ruby label: Ruby source: >- require "didit" # Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID # and DIDIT_APPLICATION_ID. didit = Didit::Client.new content = didit.transactions.generate_pdf("abcdef12-3456-7890-abcd-ef1234567890") File.binwrite("download.pdf", content) - lang: csharp label: .NET source: >- using System; using Didit; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. using var client = new DiditClient(); var content = await client.Transactions.GeneratePdfAsync("abcdef12-3456-7890-abcd-ef1234567890"); await content.SaveToAsync("download.pdf"); components: 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.