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 unassignresolutionstringResolution 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 400resolution_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 2 months ago Get caseList case activityDid this page help you?YesNo