Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

Overview

Use this method to retrieve all events related to a specific case in Case Management.

Required permissions

To use the method, you must have a role with the View case management permission.

📘
Info
This endpoint is available only in the paid version of Case Management 2.0 and does not return events for cases in earlier versions.

Request example

curl -X GET \
     'https://api.sumsub.com/resources/api/caseManagement/v2/cases/69ce2a555b353c0000000000/events?limit=100&offset=0'
     -H 'X-App-Token: <your-app-token>' \
     -H 'X-App-Access-Sig: <your-signature>' \
     -H 'X-App-Access-Ts: <unix-timestamp>'

Response explained

The response is a JSON object that contains nested objects representing events for the specified case.

Below is the response structure, along with its possible content and field descriptions.

Root variables

Field	Type	Description
`events`	Array of objects	List of event objects.
`total`	Integer	Total number of events for the case.

`events` attributes

The following table includes the events array attributes. All fields are nullable except for createdAt.

Field	Type	Description
`createdAt`	Date	Date and time when the event occurred, in the format `yyyy-MM-dd HH:mm:ss.SSS` (for example, `2025-11-07 12:18:39.071`).
`activity`	String	Event type. See the table below.
`actorSubjectName`	String	Identifier of the subject who performed the action.
`actorSubjectRole`	String	Role of the actor subject.
`targetSubjectName`	String	Name of the subject targeted by the action, if applicable.
`clientId`	String	Your identifier as a Sumsub client.
`applicantId`	String	Identifier of the applicant associated with the case.
`kytCaseId`	String	Identifier of the case the event belongs to.
`status`	String	Case status at the time of this event. See the table below.
`sourceKey`	String	Source key.
`reviewAnswer`	String	Legacy field, retained for backward compatibility.
`reviewRejectType`	String	Legacy field, retained for backward compatibility.
`kytCaseReportId`	String	Report created for the case, if this event is a report-creation event.
`kytCaseChecklistFinishedItems`	Array of strings	Checklist items marked finished at the time of this event.
`kytCaseChecklistNonFinishedItems`	Array of strings	Checklist items not yet finished at the time of this event.
`kytCaseBlueprintId`	String	Blueprint identifier at the time of the event.
`kytCaseBlueprintName`	String	Blueprint name at the time of the event.
`kytCaseCreatedType`	String	How the case was created (for example, `byOfficer`).
`kytCaseFourEyeAffectedActionsCount`	Integer	Number of actions affected by a four-eye (dual-control) review.
`kytCaseOldPriority`	String	Priority before the change.
`kytCasePriority`	String	Priority after the change.
`kytCaseOldDeadline`	Date	Deadline before the change, in the format `yyyy-MM-dd HH:mm:ss.SSS` (for example, `2025-11-07 12:18:39.071`).
`kytCaseDeadline`	Date	Deadline after the change, in the format `yyyy-MM-dd HH:mm:ss.SSS` (for example, `2025-11-07 12:18:39.071`).
`kytCaseTags`	Array of strings	Full list of tags on the case at the time of this event.
`stage`	String	Case stage at the time of this event.
`kytCaseOldName`	String	Case name before the change.
`kytCaseName`	String	Case name after the change.
`addedTags`	Array of strings	Tags added to this event.
`deletedTags`	Array of strings	Tags removed from this event.
`kytCaseBlueprintChangeType`	String	Type of blueprint change (for example, upgrade/downgrade).
`kytCaseActionAmlCaseId`	String	AML case linked to a case action.
`kytCaseActionAmlEntityId`	String	AML entity linked to a case action.
`kytCaseActionAmlCaseType`	String	Type of the linked AML case.
`noteId`	String	Related note, if the event is a note action.

Event types

The following table describes the event types (events.activity values).

Event Type	Description
`service:created:kytCase`	New case is created.
`kytCase:changed:status`	Status of a case is changed.
`user:escalated:kytCase`	User escalates a case.
`user:assigned:kytCase`	User assigns a case to themselves or another user.
`user:changed:kytCaseName`	User changes the name of a case.
`user:changed:kytCaseTag`	User changes the tag(s) associated with a case.
`user:created:kytCaseReport`	User creates a report for a case.
`user:submitted:kytCaseChecklist`	User submits a checklist for a case.
`user:created:kytCaseNote`	User adds a new note to a case.
`user:changed:kytCaseNote`	User edits an existing note on a case.
`user:removed:kytCaseNote`	User deletes a note from a case.
`user:changed:kytCasePriority`	User changes the priority level of a case.
`user:changed:kytCaseDeadline`	User changes the deadline of a case.
`kytCase:added:kytTxn`	Transactions are added to a case.
`kytCase:removed:kytTxn`	Transactions are removed from a case.
`user:reset:kytFourEyeMakerReview`	User resets the maker's review in the four-eye (dual control) process.
`user:applied:kytFourEyeAction`	User applies an action as part of the four-eye review process.
`user:removed:kytFourEyeAction`	User removes a previously applied four-eye review action.
`user:submitted:kytFourEyeMakerReview`	Maker submits the four-eye review to the checker.
`user:finalized:kytFourEyeMakerReview`	Checker finalizes the four-eye review.
`user:requested:caseAnalytics`	User requests Case Management analytics.
`user:created:kytCaseAiSummary`	User generates an AI summary on the case page.

`status` values

Status	Description
`open`	Case is open and awaiting action.
`awaitingUser`	Case is waiting on a response/action from the end user.
`blocked`	Case is blocked.
`resolvedFalsePositive`	Resolved — flagged as a false positive.
`resolvedPotentialThreat`	Resolved — flagged as a potential threat.

📘
Note
resolvedFalsePositive and resolvedPotentialThreat are the two terminal (resolved) statuses; the other three represent an open case.

Response examples

If the request is successfully sent and processed, you will get a response like the one below.

{
  "events": [
    {
      "createdAt": "2026-08-18 10:15:32.071",
      "activity": "user:changed:kytCasePriority",
      "actorSubjectName": "[email protected]",
      "kytCaseId": "5f4a8c2e1234567890abcdef",
      "status": "inProgress",
      "kytCaseOldPriority": "medium",
      "kytCasePriority": "high"
    },
    {
      "createdAt": "2026-08-18 11:02:07.072",
      "activity": "user:changed:kytCaseDeadline",
      "actorSubjectName": "[email protected]",
      "kytCaseId": "5f4a8c2e1234567890abcdef",
      "status": "inProgress",
      "kytCaseOldDeadline": "2026-08-20 00:00:00.000",
      "kytCaseDeadline": "2026-08-25 00:00:00.000"
    },
    {
      "createdAt": "2026-08-19 09:40:11.073",
      "activity": "user:changed:kytCaseName",
      "actorSubjectName": "[email protected]",
      "kytCaseId": "5f4a8c2e1234567890abcdef",
      "status": "resolved",
      "kytCaseBlueprintId": "649f1a2b3c4d5e6f7a8b9c0d",
      "kytCaseBlueprintName": "High-risk transaction review",
      "kytCaseOldName": "Case #10432",
      "kytCaseName": "Suspicious wire transfer - ACME Corp",
      "addedTags": [
        "escalated"
      ],
      "deletedTags": [
        "needs-review"
      ],
      "noteId": "66b1f2a3c4d5e6f7a8b9c0d1"
    }
  ],
  "total": 3
}

If the request fails, you will receive an HTTP response containing an error code along with a message explaining the error. For example:

{
  "code": 400,
  "correlationId": "5376e64f1a6b09d36efc259e13450880",
  "description": "Invalid id '000'"
}

Overview

Required permissions

Info

Request example

Response explained

Root variables

events attributes

Event types

status values

Note

Response examples

`events` attributes

`status` values