Didit Case Management API

Overview

A case is a compliance investigation anchored to exactly one subject: one user or one business. Sessions, business sessions and transactions of that same subject can be linked to it. Your team (or your integration) works the case from OPEN to RESOLVED with a full audit trail, and can file a Financial Intelligence Unit (FIU) report from it.

Key facts:

• Lifecycle has three statuses: OPEN, AWAITING_USER, RESOLVED. Resolution is FALSE_POSITIVE, VALID_THREAT, INCONCLUSIVE, REQUIREMENTS_NOT_MET or REQUIREMENTS_SATISFIED; only VALID_THREAT feeds the shared fraud index. Priority is LOW, MEDIUM (default) or HIGH.
• One subject per case. Linking a session, business session or transaction that belongs to another user or business returns 400.
• A blueprint (called a review policy in the console) decides assignment, escalation, transfer, 4-eyes approval, a required resolution note, the checklist and which sections the case page shows.
• Cases are created by four sources: MANUAL (console or API), AML_SCREENING (ongoing-monitoring hits), TRANSACTION_RULE (a rule with the Create case effect) and WORKFLOW_BUILDER (a Create case node). API-created cases are always MANUAL.
• Every endpoint is scoped to one organization and one application: https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/...
• Actions taken with an API key have no person attached: actor_email and actor_name on events and notes, and resolved_by_email, are null.

Pricing: No list price is published for these endpoints; check didit.me/pricing.

API Reference: https://docs.didit.me/management-api/cases/list Feature guides: https://docs.didit.me/console/case-management/cases | https://docs.didit.me/console/case-management/blueprints | https://docs.didit.me/console/case-management/four-eyes | https://docs.didit.me/console/case-management/fiu-reports