> ## 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 将案件结案为误报或有效威胁。了解清单门控、必填备注门控以及 4-eyes 暂存机制。 解决案件 API 提示词 将提示词复制到剪贴板 \

\`Resolve a case through the Management API.

Endpoint:
POST https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/resolve/

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

Request body:
\{"resolution": "FALSE_POSITIVE", "note": "Confirmed legitimate activity after reviewing documents."}
\- resolution is required: FALSE_POSITIVE (no concern found) | VALID_THREAT (concern confirmed) | INCONCLUSIVE | REQUIREMENTS_NOT_MET | REQUIREMENTS_SATISFIED.
\- note is required only when the case's blueprint has require_resolution_note enabled.
\- checker is optional and only for a blueprint with a four-eyes checker step: the user uuid of the member who must approve the resolution (the same id as assigned_to.uuid on a case, or members[].user_id on a review team). Omit it or send null to leave the resolution to the checker queue.

Behavior:
\- Blocked with 400 if the blueprint's checklist is not optional and any item is incomplete - response lists the incomplete item labels.
\- Blocked with 400 if the blueprint requires a note and none was given.
\- If the blueprint has a four_eyes_checker_blueprint configured, the resolution is staged (case.pending_resolution) and the case moves to that checker blueprint's queue instead of closing - status stays OPEN. A different user must then call approve or reject-approval.
\- Submit a four-eyes resolution as a console member. A resolution an API key submits has no recorded maker (pending_resolution.maker_email is null), so approve and reject-approval return 403 {"detail": "Case has no recorded maker for this pending resolution; approve is not permitted."} for every caller.
\- Otherwise the case closes immediately: status becomes RESOLVED, resolved_at and resolved_by_email are set.
\- On a four-eyes blueprint with checker, only that member can approve or reject the staged resolution, and the response's checker {member_uuid, name, email} names them. Any other caller, including an API key, gets 403 on approve and reject-approval. Without checker, the response's checker is null and the checker blueprint's queue decides.

Example call:
curl -X POST "https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/resolve/" \
-H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"resolution": "FALSE_POSITIVE", "note": "Confirmed legitimate activity."}'

Response 200: CaseDetail. Check pending_resolution to tell staged-for-approval apart from a completed resolution.

Failure modes:
\- 400 - incomplete checklist, or missing required note (a list of strings).
\- 400 - when checker is sent, in the order they fire:
\- ["Reviewer access could not be verified. Try again."] or ["Choose an active reviewer with case access to this application."] - the member could not be checked, or is not an active reviewer with case access.
\- {"checker": ["The officer who submitted the resolution cannot be its checker."]} - you named the officer who is resolving.
\- {"checker": ["This review policy has no checker step, so the case resolves directly."]} - the case's blueprint has no four-eyes checker step.
\- 401/403 - auth/permission errors. A key with restricted access gets 403 {"detail": "This API key has no access to this endpoint."} (cases need a full-access key). A console member token needs write:cases.
\- 404 - case not found.

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

\
粘贴到 解决一个案件。如果其蓝图与[四眼复核](https://docs.didit.me/zh/console/case-management/four-eyes.md)的复核蓝图配对，此操作会暂存解决结果，而不是直接关闭案件。请检查响应中的 `pending_resolution` 字段，以区分这两种结果。## 指定复核人在包含四眼复核步骤的蓝图上，请传入 `checker`，其值为必须批准该解决结果的成员的用户 UUID。 此后只有该成员可以批准或拒绝该结果，其他人（包括 API 密钥）都会收到 `403`。 在该结果被批准、被拒绝，或因证据变更而退回重新审核之前，案件的 `checker` 字段会显示该复核人。 如果未传入 `checker`，该解决结果将在复核蓝图的队列中等待。 该成员必须拥有本应用的案件访问权限，且不能是提交该解决结果的人员。 在不包含复核步骤的蓝图上，传入 `checker` 会返回 `400`。## 四眼复核需要控制台成员提交需要进行四眼复核的解决结果时，请以控制台成员身份操作，而不是使用 API 密钥。 由 API 密钥提交的解决结果没有可记录的制单人，因此批准和拒绝批准操作对所有调用方都会返回 `403`，包括指定的复核人。## 访问权限案件相关 endpoint 需要具备完全访问权限的 [API 密钥](https://docs.didit.me/zh/console/api-keys.md)。 权限受限的密钥会收到 `403`。## 相关链接- [四眼复核（控制台）](https://docs.didit.me/zh/console/case-management/four-eyes.md) - [获取案件](https://docs.didit.me/zh/management-api/cases/get.md) - [检查清单（控制台）](https://docs.didit.me/zh/console/case-management/checklist.md) - [批量更新状态](https://docs.didit.me/zh/management-api/cases/bulk-status.md) ## OpenAPI ````yaml zh/openapi-25.json POST /v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/resolve/ 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}/cases/{case_uuid}/resolve/: post: tags: - Cases summary: 解决案件 description: >- 使用以下五种处置结果之一解决该案件：FALSE_POSITIVE（未发现隐患）、VALID_THREAT（隐患已确认）、INCONCLUSIVE、REQUIREMENTS_NOT_MET 或 REQUIREMENTS_SATISFIED。如果蓝图的清单不是可选的且仍有未完成项，或者蓝图要求提供处置备注但未提供，则会被拦截并返回 400。当案件的蓝图包含双人复核步骤（four_eyes_checker_blueprint）时，处置结果会被暂存（case.pending_resolution），且案件会移至复核蓝图而不是立即解决；必须由另一位工作人员调用 approve 或 reject-approval。请以控制台成员身份提交双人复核处置：由 API 密钥提交的处置没有记录经办人，因此 approve 和 reject-approval 对任何调用方都会返回 403。在双人复核蓝图上，您可以使用 `checker` 指定必须批准的成员：届时只有该成员可以批准或拒绝该处置，且响应中的 `checker` 会显示该成员。如果不指定 `checker`，处置将在复核蓝图的队列中等待。为没有复核步骤的蓝图发送 `checker` 将返回 400。 operationId: resolve_case parameters: - name: organization_id in: path required: true schema: type: string format: uuid description: 组织 UUID。 - name: application_id in: path required: true schema: type: string format: uuid description: 应用 UUID。 - name: case_uuid in: path required: true schema: type: string format: uuid example: c1a5e000-0000-4000-8000-000000000001 description: 案件 UUID。 requestBody: required: true content: application/json: schema: type: object required: - resolution properties: resolution: type: string enum: - FALSE_POSITIVE - VALID_THREAT - INCONCLUSIVE - REQUIREMENTS_NOT_MET - REQUIREMENTS_SATISFIED note: type: string nullable: true description: 当蓝图设置了 require_resolution_note 时必填。 checker: type: string format: uuid nullable: true description: >- 仅限双人复核蓝图。必须批准此决议的成员用户 uuid（与案件上的 `assigned_to.uuid` 或审核团队中的 `members[].user_id` 相同）。该成员必须对此应用具有案件访问权限，且不能是提交该决议的工作人员。省略该字段或发送 null 可将决议交由复核员队列处理。 examples: Resolve: value: resolution: FALSE_POSITIVE note: Confirmed legitimate activity after reviewing documents. Four-eyes blueprint with a named checker: value: resolution: VALID_THREAT note: Document tampering confirmed. checker: 3fa85f64-5717-4562-b3fc-2c963f66afa6 responses: '200': description: 已解决，或已暂存以待双人复核。 content: application/json: schema: $ref: '#/components/schemas/CaseDetail' '400': description: >- 该处置被拒绝。非字段错误以字符串列表形式返回：清单未完成、缺少必填备注，或者 `checker` 无法核验或不是对此应用具有案件访问权限的活跃审核员。`checker` 错误以该字段为键返回：指定成员是提交处置的工作人员，或者案件蓝图没有复核步骤。 content: application/json: schema: oneOf: - type: array items: type: string - type: object additionalProperties: type: array items: type: string examples: Incomplete checklist: value: - >- Case has incomplete checklist items: Verify source of funds Resolution note required: value: - A resolution note is required to resolve this case. Reviewer access could not be verified: value: - Reviewer access could not be verified. Try again. Checker is not an active reviewer: value: - >- Choose an active reviewer with case access to this application. Checker is the submitting officer: value: checker: - >- The officer who submitted the resolution cannot be its checker. Policy has no checker step: value: checker: - >- This review policy has no checker step, so the case resolves directly. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X POST 'https://verification.didit.me/v3/organization/11111111-2222-3333-4444-555555555555/application/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/cases/c1a5e000-0000-4000-8000-000000000001/resolve/' \ -H 'x-api-key: YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"resolution": "FALSE_POSITIVE", "note": "Confirmed legitimate activity after reviewing documents."}' - lang: python label: Python source: |- from didit import Didit # Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID # and DIDIT_APPLICATION_ID. client = Didit() result = client.cases.resolve( "c1a5e000-0000-4000-8000-000000000001", resolution="FALSE_POSITIVE", note="Confirmed legitimate activity after reviewing documents.", ) print(result) - lang: javascript label: Node.js source: >- import Didit from "@didit-protocol/sdk-node"; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. const didit = new Didit(); const result = await didit.cases.resolve("c1a5e000-0000-4000-8000-000000000001", { resolution: "FALSE_POSITIVE", note: "Confirmed legitimate activity after reviewing documents.", }); console.log(result); - 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\nresult, err := client.Cases.Resolve(ctx, \"c1a5e000-0000-4000-8000-000000000001\", didit.CasesResolveParams{\n\tResolution: \"FALSE_POSITIVE\",\n\tNote: didit.String(\"Confirmed legitimate activity after reviewing documents.\"),\n})\nif err != nil {\n\tlog.Fatal(err)\n}\nfmt.Printf(\"%+v\\n\", result)" - lang: java label: Java source: >- import me.didit.Didit; import me.didit.types.CasesResolveParams; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. Didit client = new Didit(); var result = client.cases().resolve("c1a5e000-0000-4000-8000-000000000001", CasesResolveParams.builder() .resolution(CasesResolveParams.Resolution.of("FALSE_POSITIVE")) .note("Confirmed legitimate activity after reviewing documents.") .build()); System.out.println(result); - lang: php label: PHP source: >- cases->resolve('c1a5e000-0000-4000-8000-000000000001', [ 'resolution' => 'FALSE_POSITIVE', 'note' => 'Confirmed legitimate activity after reviewing documents.', ]); print_r($result->toArray()); - lang: ruby label: Ruby source: |- require "didit" # Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID # and DIDIT_APPLICATION_ID. didit = Didit::Client.new result = didit.cases.resolve( "c1a5e000-0000-4000-8000-000000000001", resolution: "FALSE_POSITIVE", note: "Confirmed legitimate activity after reviewing documents." ) puts result.to_h - lang: csharp label: .NET source: >- using System; using System.Text.Json; using Didit; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. using var client = new DiditClient(); var result = await client.Cases.ResolveAsync("c1a5e000-0000-4000-8000-000000000001", new CasesResolveParams { Resolution = "FALSE_POSITIVE", Note = "Confirmed legitimate activity after reviewing documents.", }); Console.WriteLine(JsonSerializer.Serialize(result)); components: schemas: CaseDetail: type: object properties: uuid: type: string format: uuid case_number: type: string nullable: true title: type: string status: type: string enum: - OPEN - AWAITING_USER - RESOLVED resolution: type: string enum: - FALSE_POSITIVE - VALID_THREAT - INCONCLUSIVE - REQUIREMENTS_NOT_MET - REQUIREMENTS_SATISFIED nullable: true resolution_notes: type: string nullable: true priority: type: string enum: - LOW - MEDIUM - HIGH source: type: string enum: - MANUAL - AML_SCREENING - TRANSACTION_RULE - WORKFLOW_BUILDER tags: type: array items: type: string subject: $ref: '#/components/schemas/CaseSubject' assigned_to: $ref: '#/components/schemas/CaseAssignee' assigned_at: type: string format: date-time nullable: true team: $ref: '#/components/schemas/CaseTeamSummary' due_at: type: string format: date-time nullable: true resolved_at: type: string format: date-time nullable: true resolved_by_email: type: string nullable: true pending_resolution: type: object nullable: true description: 仅在双人复核（4-eyes）决议暂存于审核员蓝图、等待批准或拒绝批准时设置。 properties: resolution: type: string enum: - FALSE_POSITIVE - VALID_THREAT - INCONCLUSIVE - REQUIREMENTS_NOT_MET - REQUIREMENTS_SATISFIED resolution_notes: type: string nullable: true maker_email: type: string format: email nullable: true description: >- 提交处置决议的合规官邮箱。由 API 密钥提交时为 Null：该处置决议没有记录的制定者，因此针对所有调用方，approve 和 reject-approval 均返回 403。 maker_name: type: string nullable: true maker_user_id: type: string format: uuid nullable: true description: 提交处理决定的人员的成员用户 uuid。由 API 密钥提交时为 null。该成员不能被指定为 `checker`。 maker_blueprint_id: type: string format: uuid staged_at: type: string format: date-time checker: $ref: '#/components/schemas/CaseChecker' metadata: type: object blueprint: $ref: '#/components/schemas/CaseBlueprintDetail' notes: type: array items: $ref: '#/components/schemas/CaseNote' description: 最新的 50 条备注。 events: type: array items: $ref: '#/components/schemas/CaseEvent' description: 最新的 100 个事件。 links: type: array items: $ref: '#/components/schemas/CaseLink' links_count: type: integer notes_count: type: integer checklist_items: type: array items: $ref: '#/components/schemas/CaseChecklistItem' created_at: type: string format: date-time updated_at: type: string format: date-time CaseSubject: type: object nullable: true description: 该案件所绑定的单个用户或企业。 properties: type: type: string enum: - user - business uuid: type: string format: uuid name: type: string external_id: type: string nullable: true description: 主体的 vendor_data。 country: type: string nullable: true description: >- 主体的三位字母国家/地区代码（ISO 3166-1 alpha-3），若未知则为 null。对于企业，为其注册国家/地区。对于个人，为其验证中的身份证件的签发国家/地区；拥有多个国家/地区证件的个人将显示其中之一，并且可能会出现类似 `XXA` 的 ICAO 证件代码。 example: ESP portrait: type: string format: uri nullable: true description: >- 个人肖像图像的短期签名 URL。对于企业始终为 null，对于没有肖像的人员为 null。该 URL 会过期，因此读取案件时请下载图像，而不是直接存储 URL。 CaseAssignee: type: object nullable: true properties: uuid: type: string format: uuid full_name: type: string email: type: string format: email CaseTeamSummary: type: object nullable: true description: >- 负责该案件的审核团队；没有团队负责时为 null。当路由规则将案件分配给其团队之一时，路由系统会对其进行设置。使用 `PATCH .../cases/{case_uuid}/`（`team`）进行修改或清除。 properties: uuid: type: string format: uuid name: type: string CaseChecker: type: object nullable: true description: >- 被指定批准或拒绝待决决定的成员。仅当双人复核（four-eyes）决议等待指定复核员时设置。在无待决事项、待决决议在复核员队列中等待，以及决议已获批准、被拒绝或因证据变更而退回重新审核后，该值为 null。 properties: member_uuid: type: string format: uuid description: 成员的用户 UUID：在您解决案件时作为 `checker` 传入的值。 name: type: string nullable: true description: 成员的姓名，未知时为 null。 email: type: string format: email CaseBlueprintDetail: type: object properties: uuid: type: string format: uuid name: type: string maxLength: 24 description: type: string nullable: true assignment_method: type: string enum: - MANUAL - AUTOMATIC assignee_pool: type: array items: type: string format: uuid max_active_cases: type: integer nullable: true escalation_enabled: type: boolean transfer_enabled: type: boolean require_resolution_note: type: boolean is_active: type: boolean preset_key: type: string nullable: true created_at: type: string format: date-time escalation_blueprint: type: string format: uuid nullable: true escalation_blueprint_name: type: string nullable: true four_eyes_checker_blueprint: type: string format: uuid nullable: true four_eyes_checker_blueprint_name: type: string nullable: true content_config: type: object description: 控制案件页面上显示哪些标签页和字段的六个可切换板块。未知的板块或键将被拒绝。 properties: checklist: type: object properties: enabled: type: boolean optional: type: boolean description: 为 true 时，可以在核对清单项未完成的情况下解决案件。 items: type: array items: type: object properties: label: type: string maxLength: 255 order: type: integer aml_control: type: object properties: enabled: type: boolean financial: type: boolean identity: type: boolean identity: type: object properties: enabled: type: boolean personal_information: type: boolean applicant_tags: type: boolean contact_information: type: boolean risk_overview: type: boolean poi_documents: type: boolean poa_documents: type: boolean verifications: type: object properties: enabled: type: boolean summary: type: boolean reporting: type: object properties: enabled: type: boolean fiu_reports: type: boolean financial: type: object properties: enabled: type: boolean payment_methods: type: boolean transactions: type: boolean creation_sources: type: array description: 当前将新案件路由到此蓝图的连接器。 items: type: object properties: kind: type: string enum: - aml - rule - workflow id: type: string name: type: string receives_escalation_from: type: array description: 升级目标指向此蓝图的其他蓝图。 items: type: object properties: id: type: string name: type: string updated_at: type: string format: date-time version: type: integer readOnly: true default_deadline_hours: type: integer nullable: true minimum: 1 maximum: 8760 CaseNote: type: object properties: uuid: type: string format: uuid comment: type: string actor_email: type: string format: email nullable: true actor_name: type: string nullable: true mentioned_emails: type: array items: type: string format: email is_internal: type: boolean attachments: type: array items: type: object properties: s3_key: type: string filename: type: string file_size: type: integer url: type: string format: uri tags: type: array items: type: string created_at: type: string format: date-time CaseEvent: type: object properties: uuid: type: string format: uuid event_type: type: string enum: - CREATED - STATUS_CHANGED - ASSIGNED - UNASSIGNED - RESOLVED - REOPENED - LINK_ADDED - LINK_REMOVED - NOTE_ADDED - NOTE_PINNED - NOTE_UNPINNED - PRIORITY_CHANGED - DUE_DATE_CHANGED - TAG_ADDED - TAG_REMOVED - ESCALATED - TRANSFERRED - CHECKLIST_COMPLETED - REPORT_CREATED - REPORT_FINALIZED - SUBMITTED_FOR_APPROVAL - APPROVAL_GRANTED - APPROVAL_REJECTED - ENTITY_ACTION - APPROVAL_INVALIDATED - CUSTOMER_REQUEST - STAGE_CHANGED - TEAM_CHANGED - CHECKER_ASSIGNED - CHECKER_UNASSIGNED actor_email: type: string format: email nullable: true actor_name: type: string nullable: true previous_status: type: string enum: - OPEN - AWAITING_USER - RESOLVED nullable: true new_status: type: string enum: - OPEN - AWAITING_USER - RESOLVED nullable: true metadata: type: object created_at: type: string format: date-time CaseLink: type: object properties: uuid: type: string format: uuid linked_entity_type: type: string enum: - session - business_session - transaction nullable: true linked_entity_uuid: type: string format: uuid nullable: true linked_entity_summary: type: object nullable: true description: >- 对于 session 和 business_session 链接为 session_id/session_number/status；对于 transaction 链接为 uuid/txn_id/status。 created_at: type: string format: date-time CaseChecklistItem: type: object properties: uuid: type: string format: uuid label: type: string maxLength: 255 is_completed: type: boolean completed_by: type: string format: email nullable: true completed_at: type: string format: date-time nullable: true order: 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.