Case Token

Parameters for Editing an Existing Comment on a Case

case_token

• Type: uuid
• Required: Yes
• Description: Globally unique identifier for the case.

comment_token

• Type: uuid
• Required: Yes
• Description: Globally unique identifier for the comment.

comment

• Type: string
• Required: Yes
• Description: New text of the comment.

actor_token

• Type: string
• Required: No
• Description: Optional client-provided identifier for the actor performing this action. This value is supplied by the client (for example, your own internal user ID) and is not authenticated by Lithic.

200 Case Activity Entry

Object Structure

• token
  • Type: uuid
  • Required: Yes
  • Description: Globally unique identifier for the activity entry.
• entry_type
  • Type: string
  • Enum: Yes
  • Required: Yes
  • Description: The case field that changed, or the action that was taken, in an activity entry:
    • STATUS - The case status changed
    • TITLE - The case title changed
    • ASSIGNED_TO - The case assignee changed
    • RESOLUTION_OUTCOME - The resolution outcome was set or changed
    • RESOLUTION_NOTES - The resolution notes were set or changed
    • TAGS - The case tags changed
    • PRIORITY - The case priority changed
    • COMMENT - A comment was added or edited
    • FILE - A file was attached to the case
• actor_token
  • Type: string | null
  • Required: Yes
  • Description: Identifier of the actor that produced the activity entry.
• previous_value
  • Type: string | null
  • Required: Yes
  • Description: Previous value of the changed field, when applicable.
• new_value
  • Type: string | null
  • Required: Yes
  • Description: New value of the changed field, when applicable.
• created
  • Type: date-time
  • Required: Yes
  • Description: Date and time at which the activity entry was created.

Example Curl Request

curl --request PATCH \
     --url https://sandbox.lithic.com/v1/transaction_monitoring/cases/case_token/comments/comment_token \
     --header 'accept: application/json' \   
     --header 'content-type: application/json' \  
     --data '
{
  "comment": "string",
  "actor_token": "string"
}
'

Example Response

{
  "token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "entry_type": "STATUS",
  "actor_token": "string",
  "previous_value": "string",
  "new_value": "string",
  "created": "2026-07-18T00:25:55.136Z"
}