How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Didit Cases API

The Cases API from Didit — 24 operation(s) for cases.

Didit Cases API is one of 17 APIs that Didit publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cases. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 30 operations across 24 paths, and defines 10 schemas. It is described by OpenAPI 3.0.0, at version 3.0.0.

Requests are made against a single base URL, https://verification.didit.me.

30 operations 24 paths 10 schemas 3 DELETE10 GET2 PATCH15 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.0.0
Base URL
https://verification.didit.me
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Didit Cases API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). An API key is passed in the header as X-Transaction-Token (TransactionTokenAuth). An API key is passed in the header as Session-Token (SessionTokenAuth).

  • TransactionTokenAuth — Short-lived scoped token minted by your backend via POST /v3/transactions/sdk-token/. Used by the Didit SDKs on the device-facing /v1/transactions/ endpoints.
  • SessionTokenAuth — Short-lived token returned in the sessiontoken field of POST /v3/session/. Used by the hosted verification flow (and custom sandbox UIs) to call session-scoped…

Paths & Operations 30

Across 24 paths, the API surfaces 30 operations — 3 DELETE, 10 GET, 2 PATCH, 15 POST. Each is listed below with its method, path, parameters, and response codes.

Cases 30
GET
/v3/organization/{organization_id}/application/{application_id}/cases/
List cases
list_cases 17 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/
Create case
create_case 2 params body → 201400
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/
Get case
get_case 3 params → 200404
PATCH
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/
Update case
update_case 3 params body → 200
DELETE
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/
Delete case
delete_case 3 params → 204
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/assign/
Assign or unassign case
assign_case 3 params body → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/resolve/
Resolve case
resolve_case 3 params body → 200400
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/reopen/
Reopen case
reopen_case 3 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/request-info/
Request info (awaiting user)
request_case_info 3 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/escalate/
Escalate case
escalate_case 3 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/transfer/
Transfer case
transfer_case 3 params body → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/approve/
Approve staged resolution (4-eyes)
approve_case_resolution 3 params → 200403409
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/reject-approval/
Reject staged resolution (4-eyes)
reject_case_resolution 3 params body → 200403409
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/entity-actions/
Apply entity action
apply_case_entity_action 3 params body → 200400
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/print/
Print case (PDF)
print_case 3 params → 200
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/notes/
List case notes
list_case_notes 5 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/notes/
Create case note
create_case_note 3 params body → 201
DELETE
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/notes/{note_uuid}/
Delete case note
delete_case_note 4 params → 204
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/notes/presign/
Upload note attachment
upload_case_note_attachment 3 params body → 201400
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/notes/presign/
Get note attachment URL
get_case_note_attachment_url 4 params → 200404
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/links/
List case links
list_case_links 3 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/links/
Add case link
create_case_link 3 params body → 201400
DELETE
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/links/{link_uuid}/
Remove case link
delete_case_link 4 params → 204
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/events/
List case events
list_case_events 5 params → 200
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/checklist/
List case checklist
list_case_checklist 3 params → 200
PATCH
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/checklist/{item_uuid}/
Toggle checklist item
toggle_case_checklist_item 4 params body → 200
GET
/v3/organization/{organization_id}/application/{application_id}/cases/{case_uuid}/aml/
List case AML hits
list_case_aml_hits 3 params → 200
GET
/v3/organization/{organization_id}/application/{application_id}/cases/statistics/
Case analytics
get_case_analytics 4 params → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/bulk/status/
Bulk update case status
bulk_update_case_status 2 params body → 200
POST
/v3/organization/{organization_id}/application/{application_id}/cases/bulk/assign/
Bulk assign cases
bulk_assign_cases 2 params body → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CaseDetail (26 properties), CaseListItem (24 properties), CaseBlueprintDetail (20 properties), CaseNote (9 properties). Each schema is shown below with its type and property counts.

CaseLink
object
5 properties
CaseEvent
object
8 properties
CaseBlueprintDetail
object
20 properties
CaseSubject
object
The single user or business the case is anchored to.
4 properties
CaseBlueprintSummary
object
2 properties
CaseDetail
object
26 properties
CaseAssignee
object
3 properties
CaseChecklistItem
object
6 properties
CaseNote
object
9 properties
CaseListItem
object
24 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

didit-cases-api-openapi.yml Raw ↑

Other APIs Didit publishes across the network.

Didit Billing API
Didit Businesses API
Didit Case Blueprints API
Didit Customization API
Didit Questionnaires API
Didit Regulatory Reports API
Didit Report Templates API
Didit Session API
Didit Sessions API
Didit Standalone APIs API
Didit System API
Didit Transactions API
Where this information came from

This is an independent, third-party profile of Didit Cases API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.