> ## 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 提示词 将提示词复制到剪贴板 \

\`Update a case's title, priority, due date, tags or owning review team through the Management API.

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

Authentication:
Use the x-api-key header with my Didit API key.
Cases endpoints need a full-access API key: a key with restricted access gets 403.

Request body (partial: send only the fields to change, omitted fields keep their value):
\{"priority": "HIGH", "due_at": "2026-11-01T00:00:00Z", "team": ""}
\- title - string, at most 255 characters.
\- priority - LOW | MEDIUM | HIGH.
\- due_at - ISO 8601 datetime, or null to clear the deadline.
\- tags - array of strings. Replaces the whole tag list, so send every tag the case should keep.
\- team - uuid of an active review team of this application, or null to clear the team.

Getting a team uuid:
GET https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/cases/teams/ (same full-access key; a console member token needs list:cases) returns results[] with uuid, name and is_active. Only a team with is_active true is accepted.

Behavior:
\- Logs PRIORITY_CHANGED, DUE_DATE_CHANGED, TAG_ADDED, TAG_REMOVED and TEAM_CHANGED events on the case when the value changes.
\- A title change is saved without a timeline event.
\- A TEAM_CHANGED event records the previous and new team as {uuid, name} in its metadata.
\- Changing the team does not reassign the case.

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

Response 200: the updated CaseDetail, the same shape as get case, including team {uuid, name} or null.

Failure modes:
\- 400: a field failed validation, keyed by field. Example: {"team": ["Choose an active team of this application."]} when the team is inactive, deleted, or belongs to another application.
\- 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 in this application.

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

\
粘贴到 更改案件的标题、优先级、截止日期、标签或负责的审核团队。 只需发送要更改的字段，省略的字段保持原值。 `tags` 会替换整个标签列表，因此请发送该案件应保留的所有标签。## 更改负责团队将 `team` 设置为本应用中某个启用的审核团队的 uuid，或设置为 `null` 以清除该团队。 要查找团队的 uuid，请调用 `GET /v3/organization/{organization_id}/application/{application_id}/cases/teams/` 并读取 `results[].uuid`。 如果团队已停用、已删除，或属于其他应用，将返回 `400` 和 `{"team": ["Choose an active team of this application."]}`。 每次更改都会在案件时间线中添加一条 `TEAM_CHANGED` 事件，其中包含之前的团队和新的团队。 更改团队不会改变案件的指派对象。## 时间线事件更改优先级、截止日期、标签或团队时，会在案件时间线中添加 `PRIORITY_CHANGED`、`DUE_DATE_CHANGED`、`TAG_ADDED`、`TAG_REMOVED` 或 `TEAM_CHANGED` 事件。 更改标题会直接保存，不会添加时间线事件。 发送与当前值相同的字段不会添加任何事件。## 访问权限案件相关端点需要具有完全访问权限的 [API 密钥](https://docs.didit.me/zh/console/api-keys.md)。 具有受限访问权限的密钥会收到 `403`。 控制台成员令牌需要 `write:cases` 权限。## 相关内容- [获取案件](https://docs.didit.me/zh/management-api/cases/get.md) - [列出案件](https://docs.didit.me/zh/management-api/cases/list.md) - [指派和审核团队（控制台）](https://docs.didit.me/zh/console/case-management/assignment.md#团队) ## OpenAPI ````yaml zh/openapi-25.json PATCH /v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/ 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}/: patch: tags: - Cases summary: 更新案件 description: >- 更新案件的标题、优先级、截止日期、标签或所属审核团队。仅发送您想要更改的字段；省略的字段将保留其原值。`tags` 会替换整个标签列表。`team` 接受此应用中某个活跃审核团队的 uuid（可通过 `GET .../cases/teams/` 列出），或为 null 以清除团队。需要完全访问权限的 API 密钥，或者控制台成员具备 `write:cases` 权限：受限访问权限的密钥将收到 403。视情况记录 PRIORITY_CHANGED、DUE_DATE_CHANGED、TAG_ADDED、TAG_REMOVED 和 TEAM_CHANGED 事件；标题更改会被保存但不会生成时间线事件。返回更新后的案件。 operationId: update_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: false content: application/json: schema: type: object properties: title: type: string maxLength: 255 description: 新案件标题。 priority: type: string enum: - LOW - MEDIUM - HIGH due_at: type: string format: date-time nullable: true description: 新截止日期。发送 null 可清除该值。 tags: type: array items: type: string description: 完整的标签列表。它将替换当前的标签。 team: type: string format: uuid nullable: true description: 负责该案件的审核团队的 UUID。必须是此应用下的活跃团队。发送 null 可清除团队。 examples: Change priority and deadline: value: priority: HIGH due_at: '2026-11-01T00:00:00Z' Move the case to a team: value: team: 3fa85f64-5717-4562-b3fc-2c963f66afa6 Clear the team: value: team: null responses: '200': description: 已更新案件。 content: application/json: schema: $ref: '#/components/schemas/CaseDetail' '400': description: 字段验证失败。响应体以字段名为键。如果 `team` 不是此应用的活动审核团队，则会被拒绝。 content: application/json: schema: type: object additionalProperties: type: array items: type: string examples: Team not active in this application: value: team: - Choose an active team of this application. Invalid priority: value: priority: - '"URGENT" is not a valid choice.' '403': description: >- API 密钥属于另一个应用，或者是一个访问权限受限的密钥：Cases endpoint 需要具有完全访问权限的密钥。控制台成员 token 需要 `write:cases` 权限。 content: application/json: examples: Restricted API Key: summary: 受限访问权限的 API 密钥 value: detail: This API key has no access to this endpoint. Missing Privilege: summary: 不具备 write:cases 权限的 Console 成员，或其他应用的密钥 value: detail: You do not have permission to perform this action. '404': description: 在此应用中未找到案件。 content: application/json: schema: type: object properties: detail: type: string example: detail: No Case matches the given query. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X PATCH 'https://verification.didit.me/v3/organization/11111111-2222-3333-4444-555555555555/application/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/cases/c1a5e000-0000-4000-8000-000000000001/' \ -H 'x-api-key: YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"priority": "HIGH", "due_at": "2026-08-01T00:00:00Z"}' - lang: curl label: curl (change team) source: >- curl -X PATCH 'https://verification.didit.me/v3/organization/11111111-2222-3333-4444-555555555555/application/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/cases/c1a5e000-0000-4000-8000-000000000001/' \ -H 'x-api-key: YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"team": "3fa85f64-5717-4562-b3fc-2c963f66afa6"}' - 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.update( "c1a5e000-0000-4000-8000-000000000001", priority="HIGH", due_at="2026-11-01T00:00:00Z", ) 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.update("c1a5e000-0000-4000-8000-000000000001", { priority: "HIGH", due_at: "2026-11-01T00:00:00Z", }); 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.Update(ctx, \"c1a5e000-0000-4000-8000-000000000001\", didit.CasesUpdateParams{\n\tPriority: didit.Some(didit.CasesUpdateParamsPriority(\"HIGH\")),\n\tDueAt: didit.Time(time.Date(2026, 11, 1, 0, 0, 0, 0, time.UTC)),\n})\nif err != nil {\n\tlog.Fatal(err)\n}\nfmt.Printf(\"%+v\\n\", result)" - lang: java label: Java source: >- import java.time.OffsetDateTime; import me.didit.Didit; import me.didit.types.CasesUpdateParams; // Reads DIDIT_API_KEY, DIDIT_ORGANIZATION_ID // and DIDIT_APPLICATION_ID. Didit client = new Didit(); var result = client.cases().update("c1a5e000-0000-4000-8000-000000000001", CasesUpdateParams.builder() .priority(CasesUpdateParams.Priority.of("HIGH")) .dueAt(OffsetDateTime.parse("2026-11-01T00:00:00Z")) .build()); System.out.println(result); - lang: php label: PHP source: >- cases->update('c1a5e000-0000-4000-8000-000000000001', [ 'priority' => 'HIGH', 'due_at' => '2026-11-01T00:00:00Z', ]); 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.update( "c1a5e000-0000-4000-8000-000000000001", priority: "HIGH", due_at: "2026-11-01T00:00:00Z" ) 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.UpdateAsync("c1a5e000-0000-4000-8000-000000000001", new CasesUpdateParams { Priority = new CasesUpdateParamsPriority("HIGH"), DueAt = DateTimeOffset.Parse("2026-11-01T00:00:00Z"), }); 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.