Update caseCopy Pagepatch https://sandbox.lithic.com/v1/transaction_monitoring/cases/{case_token}Updates a transaction monitoring case.Path Paramscase_tokenuuidrequiredGlobally unique identifier for the case.Body ParamsParameters 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.statusstringenumStatus 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 OPENASSIGNEDIN_REVIEWESCALATEDRESOLVEDCLOSEDAllowed:OPENASSIGNEDIN_REVIEWESCALATEDRESOLVEDCLOSEDtitlestring | nullNew title for the case, or null to clear itassigneestring | nullNew assignee for the case, or null to unassignresolutionstringenumOutcome recorded when a case is resolved: CONFIRMED_FRAUD - The reviewed activity was confirmed to be fraudulent SUSPICIOUS_ACTIVITY - The activity is suspicious but not confirmed fraud FALSE_POSITIVE - The activity was legitimate and the alert was a false positive NO_ACTION_REQUIRED - No further action is required ESCALATED_EXTERNAL - The case was escalated to an external party CONFIRMED_FRAUDSUSPICIOUS_ACTIVITYFALSE_POSITIVENO_ACTION_REQUIREDESCALATED_EXTERNALAllowed:CONFIRMED_FRAUDSUSPICIOUS_ACTIVITYFALSE_POSITIVENO_ACTION_REQUIREDESCALATED_EXTERNALresolution_notesstringNotes describing the resolutiontagsobjectArbitrary key-value metadata to set on the casetags objectprioritystringenumPriority level of a case, controlling queue ordering and SLA urgencyLOWMEDIUMHIGHCRITICALAllowed:LOWMEDIUMHIGHCRITICALsla_deadlinedate-time | nullNew SLA deadline for the case, or null to clear itactor_tokenstringOptional 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 LithicResponses 200Case 400Bad Request 404Not FoundUpdated 12 days ago