Skip to main content
PATCH
Update case status, resolution, assignee, or read state

Authorizations

X-API-KEY
string
header
required

Authorization method required to allow user to access the api endpoints.

Path Parameters

id
string
required

The case id (uuid).

Body

application/json
read
boolean

Mark this case read or unread for the caller only, without a timeline entry. Session-only; API-key callers receive 403.

status
enum<string>
Available options:
open,
in_review,
resolved
resolution
enum<string>

Only "dismissed" is settable here — "escalated" is only set via POST /escalate.

Available options:
dismissed
assignee
string<email> | null
Example:

"compliance@example.com"

Response

id
string
required
workspace_id
string
required
title
string
required
status
enum<string>
required
Available options:
open,
in_review,
resolved
severity
enum<string>
required
Available options:
severe,
high,
medium,
low
source_type
enum<string>
required
Available options:
risk_screen,
sanctions_screen,
alert_event,
manual,
regulatory_filing,
tie_out_break,
corridor_discrepancy,
redemption
subject
object
required
created_at
string
required
updated_at
string
required
viewed
boolean
required

In list responses, whether this case is read for the caller.

available_actions
object[]
required

Actions supported by this source and status. Existing write permissions still apply. Resolving via set_status requires resolution=dismissed.

comments
object[]
required
resolution
enum<string> | null
Available options:
dismissed,
escalated,
paid
source_id
string | null
assignee
string | null
created_by
string | null
resolved_at
string | null
evidence_summary
object | null

What the case was opened on. A redemption case carries redemption_id, burn_time and deadline, linking it to GET /v2/redemptions/{id}.

Last modified on October 7, 2026