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

# 企业 KYB 历史：会话与报告

> 检索与 Didit 企业实体关联的全部 KYB 会话，查看注册数据和 AML 命中结果，触发重新验证，并生成可导出的合规报告。



KYB 历史记录提示
        将提示词复制到剪贴板



      
      

\<pre>

\````# Goal — read a business's full KYB history and trigger re-verification

Every KYB session is linked to the Business entity via `vendor_data`. List sessions, retrieve each decision, and create new sessions for re-KYB.

\## List every KYB session for a business

\```bash
curl -G https://verification.didit.me/v3/sessions/ \
-H "x-api-key: $DIDIT_API_KEY" \
\--data-urlencode "vendor_data=biz-acme" \
\--data-urlencode "page_size=50"
\```

KYB session payloads carry `session_kind: "business"` and `business_session_id` to distinguish them from KYC sessions.

\## Inspect a single KYB decision

\```bash
curl https://verification.didit.me/v3/session/$SESSION_ID/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
\```

KYB decisions include:

\- Company registry data (legal name, registration, status, incorporation date, addresses)
\- `key_people_checks[]` — UBOs, shareholders, directors, officers (registry-sourced and user-submitted, with role tags)
\- `aml_screenings[]` — company AML and per-person AML
\- `document_verifications[]` — uploaded docs with OCR extracts and signed image URLs

See /business-verification/response-schema for the full payload.

\## Fast path — fully verified right now?

\```bash
curl https://verification.didit.me/v3/businesses/biz-acme/ \
-H "x-api-key: $DIDIT_API_KEY"
\# data.features = { KYB: "Approved" }
\```

The Business entity's `features` map holds the latest company verification status under the `KYB` key.

\## Trigger re-KYB

Annual re-KYB or trigger-based re-checks: create a new session against the same `vendor_data`. The new session attaches to the existing Business entity.

\```bash
curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workflow_id": "wf_kyb_annual", "vendor_data": "biz-acme"}'
\```

\## Generate a KYB PDF report

\```bash
curl https://verification.didit.me/v3/session/$SESSION_ID/generate-pdf/ \
-H "x-api-key: $DIDIT_API_KEY" \
-o kyb-report.pdf
\```

PDF covers registry data, ownership structure, AML hits, document images, per-officer KYC status, questionnaires, phone verification, email verification, and IP analysis when those features are part of the workflow.

\## Resubmit vs new session

\| Scenario | Use |
\|---|---|
\| Registry needs corrected company name | Resubmit — analyst edits data and re-runs registry |
\| Additional document requested | Resubmit — business uploads the missing document |
\| Annual / trigger-based re-KYB | Create a brand new session |

\`kyb_key_people` and `kyb_registry` cannot be resubmitted directly — to re-verify a person, resubmit their child KYC session; the parent Key People feature re-aggregates automatically.

\## Share a session

\```bash
curl -X POST https://verification.didit.me/v3/session/$SESSION_ID/share/ \
-H "x-api-key: $DIDIT_API_KEY"

curl -X POST https://verification.didit.me/v3/session/import-shared/ \
-H "x-api-key: $RECEIVER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"share_token": "..."}'
\```

\## Failure modes

\- `404` — wrong `vendor_data` casing or no KYB sessions yet.
\- Stale signed image URLs — re-fetch the decision.
\- `session_kind: "user"` events in the same list — filter on `session_kind === "business"` for KYB-only handling.

\## Sources of truth

\- /business-verification/response-schema — full KYB decision payload
\- /business-verification/statuses — feature state machine
\- /entities/businesses/data-model — features map computation
\- /core-technology/reusable-kyc/overview — share / import pattern
\- /integration/integration-prompt — canonical end-to-end prompt````

\</pre>



      
      

粘贴到

企业实体所关联的每一次企业验证（KYB）会话都会永久保留在该企业实体上。您可以检索完整历史记录，查看每次会话的公司登记数据和 AML 命中结果，触发重新验证，并生成用于审计的 PDF 报告。## 列出某企业的所有企业验证 (KYB) 会话按 `vendor_data` 筛选会话列表：```bash theme={null}
curl -G https://verification.didit.me/v3/sessions/ \
  -H "x-api-key: YOUR_API_KEY" \
  --data-urlencode "vendor_data=biz-acme" \
  --data-urlencode "page_size=50"
```响应会包含所有企业验证（KYB）会话，无论其状态如何。## 了解 KYB 功能一次 KYB 会话会运行以下功能，每项功能在会话决策中都有各自的状态：| 功能 | 涵盖内容 |
| - | - |
| `KYB_REGISTRY` | 公司登记查询：是否存在、状态、身份交叉核对 |
| `AML` | 公司层面的 AML 筛查（制裁、负面新闻、观察名单） |
| `KYB_DOCUMENTS` | 证件收集与 OCR 交叉比对 |
| `KYB_KEY_PEOPLE` | 高管、UBO 和实际受益人的识别，以及可选的 KYC |企业实体上的 `features` 映射仅保存最新的公司验证状态：```json theme={null}
"features": {
  "KYB": "Approved"
}
```完整参考请见 [KYB 功能状态](https://docs.didit.me/zh/business-verification/statuses.md)。## 查看单个企业验证 (KYB) 会话```bash theme={null}
curl https://verification.didit.me/v3/session/{session_id}/decision/ \
  -H "x-api-key: YOUR_API_KEY"
```KYB 决策包括：- 公司登记数据（法定名称、注册信息、状态、成立日期、地址）
- 从登记信息中提取的高管和 UBO
- 股权结构（股权表、实际受益比例）
- 公司 AML 结果（命中项、分数）
- 每位 UBO 和高管的个人 AML 结果
- 含 OCR 提取内容的证件结果
- 决策原因代码完整 payload 请参见 [KYB 响应模式](https://docs.didit.me/zh/business-verification/response-schema.md)。## 触发重新验证年度 KYB 重新验证、基于触发器的复查或整改流程，都会以一次新会话开始：```bash theme={null}
curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "wf_kyb_annual",
    "vendor_data": "biz-acme"
  }'
```新会话会关联到现有企业实体，并在完成后更新 `features` 映射。## 重新提交与新建企业验证 (KYB) 会话| 场景 | 使用方式 |
| - | - |
| 公司登记查询需要更正公司名称 | 重新提交：分析人员编辑数据并重新运行登记查询 |
| 企业需要补充提交证件 | 重新提交：企业上传缺失的证件 |
| 年度或基于触发器的 KYB 重新验证 | 新建会话 |## 导出 KYB 报告为任意企业验证（KYB）会话生成完整的 PDF：```bash theme={null}
curl https://verification.didit.me/v3/session/{session_id}/generate-pdf/ \
  -H "x-api-key: YOUR_API_KEY" \
  -o kyb-report.pdf
```该 PDF 包含登记数据、股权结构、AML 命中结果、证件图像、高管 KYC 状态，以及包含决策原因的封面页。## 分享企业验证 (KYB) 会话适用于联盟或合作伙伴工作流：- `POST /v3/session/{session_id}/share/`：生成可分享的 token。
- `POST /v3/session/import-shared/`：在接收方导入。## 持续监控启用持续监控模式的企业实体会定期进行 AML 重新扫描。检测到新的制裁或负面新闻命中时，公司 AML 筛查结果会随之更新。您可以在会话决策的 `aml_screenings[]` 中读取更新后的结果。在控制台中配置持续监控，路径为 *Workflows → \[KYB workflow] → AML → Ongoing monitoring*。## 后续步骤> [card] [KYB 概览](https://docs.didit.me/zh/business-verification/overview.md)
>
> 企业验证（KYB）会话的端到端运作方式。> [card] [KYB 响应](https://docs.didit.me/zh/business-verification/response-schema.md)
>
> 完整决策 payload 参考。> [card] [关键人员](https://docs.didit.me/zh/entities/businesses/key-people.md)
>
> 高管、UBO 及关联用户。


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