Skip to main content
GET
curl
Didit’s Cases API retrieves an investigation and its linked records. Retrieve a case with everything needed to render a full case page: subject, blueprint (including its content_config), the newest notes and events, links, and checklist state. The case also carries its owning team, the named checker of a pending four-eyes resolution, and the subject’s country and portrait. Network links return their UUID in linked_entity_summary, without member details. See link a network to a case for subject and permission requirements.

Access

Cases endpoints need a full-access API key. A key with restricted access receives 403.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

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"

Response

Case detail.

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,
INCONCLUSIVE,
REQUIREMENTS_NOT_MET,
REQUIREMENTS_SATISFIED
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
team
object | null

The review team that owns the case, or null when no team owns it. Routing sets it when a routing rule places the case with one of its teams. Change or clear it with PATCH .../cases/{case_uuid}/ (team).

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.

checker
object | null

The member named to approve or reject the pending resolution. Set only while a four-eyes resolution waits on a named checker. Null when nothing is pending, while the pending resolution waits on the checker queue, and once the resolution is approved, rejected, or returned for a new review because the evidence changed.

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>
Last modified on November 11, 2026