---
title: "Update case"
method: PATCH
path: "/v1/transaction_monitoring/cases/{case_token}"
tags: ["Transaction Monitoring"]
---

# Update case

`PATCH /v1/transaction_monitoring/cases/{case_token}`

Updates a transaction monitoring case.

## Path parameters

- `case_token` string, uuid, required

## Request body

- UpdateCaseRequest — Parameters for updating a case. All fields are optional; omitted fields are left unchanged. The nullable fields `title`, `assignee`, and `sla_deadline` can be cleared by sending `null`.
  - `status` 'OPEN' | 'ASSIGNED' | 'IN_REVIEW' | 'ESCALATED' | 'RESOLVED' | 'CLOSED' — Status of a case as it progresses through the review workflow: - `OPEN` - The case has been created and is still collecting matching transactions - `ASSIGNED` - An analyst has been assigned and transaction collection has stopped - `IN_REVIEW` - The case is actively being investigated - `ESCALATED` - The case has been reviewed and requires additional oversight - `RESOLVED` - A determination has been made and a resolution recorded - `CLOSED` - The case is finalized
  - `title` string, nullable — New title for the case, or `null` to clear it
  - `assignee` string, nullable — New assignee for the case, or `null` to unassign
  - `resolution` string — Resolution to record on the case. Must be one of the `allowed_resolutions` configured on the case's queue, otherwise the request is rejected with a `400`
  - `resolution_notes` string — Notes describing the resolution
  - `tags` object — Arbitrary key-value metadata to set on the case
  - `priority` 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL' — Priority level of a case, controlling queue ordering and SLA urgency
  - `sla_deadline` string, date-time, nullable — New SLA deadline for the case, or `null` to clear it
  - `actor_token` string — Optional client-provided identifier for the actor performing this action, recorded on the resulting activity entry. This value is supplied by the client (for example, your own internal user ID) and is not authenticated by Lithic

## Response `200`

Case

- MonitoringCase — A transaction monitoring case
  - `token` string, uuid, required — Globally unique identifier for the case
  - `title` string, nullable, required — Short, human-readable summary of the case
  - `status` 'OPEN' | 'ASSIGNED' | 'IN_REVIEW' | 'ESCALATED' | 'RESOLVED' | 'CLOSED', required — Status of a case as it progresses through the review workflow: - `OPEN` - The case has been created and is still collecting matching transactions - `ASSIGNED` - An analyst has been assigned and transaction collection has stopped - `IN_REVIEW` - The case is actively being investigated - `ESCALATED` - The case has been reviewed and requires additional oversight - `RESOLVED` - A determination has been made and a resolution recorded - `CLOSED` - The case is finalized
  - `queue_token` string, uuid, required — Token of the queue the case belongs to
  - `priority` 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL', required — Priority level of a case, controlling queue ordering and SLA urgency
  - `assignee` string, nullable, required — Identifier of the user the case is currently assigned to
  - `rule_token` string, uuid, nullable, required — Token of the transaction monitoring rule that triggered the case
  - `resolution` string, nullable, required — Outcome recorded when the case was resolved, from the `allowed_resolutions` configured on the case's queue
  - `resolution_notes` string, nullable, required — Free-form notes describing the resolution
  - `sla_deadline` string, date-time, nullable, required — Deadline by which the case is expected to be resolved
  - `tags` object, required — Arbitrary key-value metadata associated with the case
  - `created` string, date-time, required — Date and time at which the case was created
  - `updated` string, date-time, required — Date and time at which the case was last updated
  - `resolved` string, date-time, nullable, required — Date and time at which the case was resolved
  - `collection_stopped` string, date-time, nullable, required — Date and time at which transaction collection stopped for the case
  - `entity` CaseEntity, required — The entity a case is associated with
    - `entity_type` 'CARD' | 'ACCOUNT', required — The type of entity a case is associated with: - `CARD` - The case is associated with a card - `ACCOUNT` - The case is associated with an account
    - `entity_token` string, uuid, required — Globally unique identifier for the associated entity
  - `pending_transactions` boolean, required — Whether the case still has transaction scopes pending resolution

## Other responses

- `400` — Bad Request
- `404` — Not Found

---

[API](https://skmtc.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/53ab5d4e2adb/schema)