Skip to main content
POST
curl
Resolve a case. If its blueprint pairs with a checker blueprint for 4-eyes review, this stages the resolution instead of closing the case - check the response’s pending_resolution field to tell the two outcomes apart.

Authorizations

x-api-key
string
header
required

Path Parameters

organization_id
string<uuid>
required

Organization UUID.

application_id
string<uuid>
required

Application UUID.

case_uuid
string<uuid>
required

Case UUID.

Example:

"c1a5e000-0000-4000-8000-000000000001"

Body

application/json
resolution
enum<string>
required
Available options:
FALSE_POSITIVE,
VALID_THREAT
note
string | null

Required when the blueprint sets require_resolution_note.

Response

Resolved, or staged for 4-eyes approval.

uuid
string<uuid>
case_number
string | null
title
string
status
enum<string>
Available options:
OPEN,
AWAITING_USER,
RESOLVED
resolution
enum<string> | null
Available options:
FALSE_POSITIVE,
VALID_THREAT
resolution_notes
string | null
priority
enum<string>
Available options:
LOW,
MEDIUM,
HIGH
source
enum<string>
Available options:
MANUAL,
AML_SCREENING,
TRANSACTION_RULE,
WORKFLOW_BUILDER
tags
string[]
subject
object | null

The single user or business the case is anchored to.

assigned_to
object | null
assigned_at
string<date-time> | null
due_at
string<date-time> | null
resolved_at
string<date-time> | null
resolved_by_email
string | null
pending_resolution
object | null

Set only while a 4-eyes resolution is staged on the checker blueprint, awaiting approve or reject-approval.

metadata
object
blueprint
object
notes
object[]

Newest 50 notes.

events
object[]

Newest 100 events.

notes_count
integer
checklist_items
object[]
created_at
string<date-time>
updated_at
string<date-time>