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

> Didit 可查询会话、企业会话、用户、企业、交易及交易对手所属的欺诈网络，帮助您快速识别关联风险。



网络成员资格查询 API 提示词
        将提示词复制到剪贴板



      
      

\<pre>

\`Look up which fraud networks an entity belongs to through the Management API.

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

Endpoints (all GET, all return {"results": [EntityNetworkMembership, ...]}, not paginated):
\- /v3/organization/{organization_id}/application/{application_id}/sessions/{session_id}/networks/ - resolves through the session's linked vendor user.
\- /v3/organization/{organization_id}/application/{application_id}/business-sessions/{business_session_id}/networks/ - resolves through the business session's linked vendor business.
\- /v3/organization/{organization_id}/application/{application_id}/users/{vendor_user_uuid}/networks/
\- /v3/organization/{organization_id}/application/{application_id}/businesses/{vendor_business_uuid}/networks/
\- /v3/organization/{organization_id}/application/{application_id}/transactions/{transaction_uuid}/networks/ - resolves through the transaction's backing KYC/KYB session's subject.
\- /v3/organization/{organization_id}/application/{application_id}/transactions/{transaction_uuid}/parties/{transaction_party_uuid}/networks/ - resolves through the party itself (remitter, beneficiary, or counterparty), independent of the backing session.

Example call:
curl -X GET "https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/users/{vendor_user_uuid}/networks/" \
-H "x-api-key: YOUR_API_KEY"

Response shape:
Each EntityNetworkMembership has network (NetworkListItem), subject, signal_types, signal_count, joined_at, last_seen_at.
An entity can belong to zero, one, or several networks - an empty results array is not an error.

Failure modes:
\- 404 - the session/business session/user/business/transaction/transaction party does not exist in this application, or (for the session and transaction variants) has no linked vendor user/business to look up.
\- 401/403 - auth/permission errors.

Side effects: none, pure read.

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

\</pre>



      
      

粘贴到

给定一个会话、企业会话、用户、企业、交易或交易方，即可查询它属于哪些欺诈网络。所有端点返回相同的结构 `{"results": [EntityNetworkMembership, ...]}`。因此，对于任何已有 UUID 的实体，您都可以直接调用对应端点，无需额外的查询步骤。| 实体 | 端点 | 解析方式 |
| - | - | - |
| 会话 | `GET .../sessions/{session_id}/networks/` | 会话关联的供应商用户 |
| 企业会话 | `GET .../business-sessions/{business_session_id}/networks/` | 企业会话关联的供应商企业 |
| 用户 | `GET .../users/{vendor_user_uuid}/networks/` | 供应商用户本身 |
| 企业 | `GET .../businesses/{vendor_business_uuid}/networks/` | 供应商企业本身 |
| 交易 | `GET .../transactions/{transaction_uuid}/networks/` | 交易所依托的 KYC/KYB 会话的主体 |
| 交易方 | `GET .../transactions/{transaction_uuid}/parties/{transaction_party_uuid}/networks/` | 交易方本身（汇款人、收款人或交易对手） |每个 `EntityNetworkMembership` 都包含网络摘要（`network`，结构与 [列出网络](https://docs.didit.me/zh/management-api/networks/list.md) 相同）、解析出的 `subject`、与其相连的 `signal_types`、`signal_count`，以及 `joined_at` 和 `last_seen_at`。没有欺诈关联的实体会返回空的 `results` 数组，而不是 404。> [!NOTE]
>
> 交易端点通过交易所依托的会话主体来解析成员资格。交易方端点则直接通过交易方本身来解析。对于不是该交易自身 KYC 主体的汇款人或收款人，后者正是您需要的方式。## 相关- [列出网络](https://docs.didit.me/zh/management-api/networks/list.md)
- [获取网络](https://docs.didit.me/zh/management-api/networks/get.md)
- [网络成员](https://docs.didit.me/zh/management-api/networks/members.md)


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