> ## 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，将案件转移至同一应用下的另一个有效蓝图，前提是当前蓝图允许转移。 转移案件 API 提示词 将提示词复制到剪贴板 \

\`Move a case to a different blueprint through the Management API.

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

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

Request body:
\{"target_blueprint": ""}

Behavior:
\- Requires the case's current blueprint to have transfer_enabled - otherwise 400.
\- target_blueprint must be an active blueprint of the same application - otherwise 400.
\- Reseeds the checklist from the new blueprint if the case had no checklist items yet, and auto-assigns if the new blueprint uses AUTOMATIC assignment.
\- Logs a TRANSFERRED event.

Example call:
curl -X POST "https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/transfer/" \
-H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"target_blueprint": ""}'

Response 200: CaseDetail with the new blueprint attached.

Failure modes:
\- 400 - transfer not enabled on the current blueprint, or target_blueprint is not an active blueprint of the same application.
\- 401/403 - auth/permission errors.

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

\
粘贴到 将案件整体转移到另一个蓝图，这与[升级](https://docs.didit.me/zh/console/case-management/blueprints.md#升级与转移)不同：升级始终只会路由到一个固定目标。只有当案件当前所属的蓝图已设置 `transfer_enabled` 时，才能进行转移。## 相关内容- [蓝图（控制台）](https://docs.didit.me/zh/console/case-management/blueprints.md) - [解决案件](https://docs.didit.me/zh/management-api/cases/resolve.md) ## OpenAPI ````yaml zh/openapi-25.json POST /v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/transfer/ 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}/transfer/: post: tags: - Cases summary: 移交案件 description: >- 将案件移动到同一应用下的另一个处于活动状态的 blueprint。要求当前 blueprint 已启用 transfer_enabled，否则返回 400。 operationId: transfer_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: - target_blueprint properties: target_blueprint: type: string format: uuid example: target_blueprint: b1de0000-0000-4000-8000-000000000002 responses: '200': description: 案件已转移。 content: application/json: schema: $ref: '#/components/schemas/CaseDetail' 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/transfer/' \ -H 'x-api-key: YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"target_blueprint": "b1de0000-0000-4000-8000-000000000002"}' - 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.transfer( "c1a5e000-0000-4000-8000-000000000001", target_blueprint="b1de0000-0000-4000-8000-000000000002", ) 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.transfer("c1a5e000-0000-4000-8000-000000000001", { target_blueprint: "b1de0000-0000-4000-8000-000000000002", }); 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.Transfer(ctx, \"c1a5e000-0000-4000-8000-000000000001\", didit.CasesTransferParams{\n\tTargetBlueprint: \"b1de0000-0000-4000-8000-000000000002\",\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.CasesTransferParams; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. Didit client = new Didit(); var result = client.cases().transfer("c1a5e000-0000-4000-8000-000000000001", CasesTransferParams.builder() .targetBlueprint("b1de0000-0000-4000-8000-000000000002") .build()); System.out.println(result); - lang: php label: PHP source: >- cases->transfer('c1a5e000-0000-4000-8000-000000000001', [ 'target_blueprint' => 'b1de0000-0000-4000-8000-000000000002', ]); 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.transfer( "c1a5e000-0000-4000-8000-000000000001", target_blueprint: "b1de0000-0000-4000-8000-000000000002" ) 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.TransferAsync("c1a5e000-0000-4000-8000-000000000001", new CasesTransferParams { TargetBlueprint = "b1de0000-0000-4000-8000-000000000002", }); 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.