d3c75c2a2f1d
Assign or Close
Path parameters
Request body
status
ID of a Staff user or provider to whom the chat will be assigned. If status is "assigned", there must be either an "assignee" or a "groupAssignee"
ID of a Group to whom the chat will be assigned. If status is "assigned", there must be either an "assignee" or a "groupAssignee"
ID of a ChatActivityStatusReason to specify why a chat was closed. When status is closed, this field is mandatory, and sometimes the "description" is also mandatory.
Description associated with a ChatActivityStatusReason to specify why a chat was closed. Some ChatActivitiesStatusReasons require a description.
Response
ChatActivity updated
Luma's internal ID of an object.
The ID of the root account user.
Flag for logical deletion where 1 means deleted.
The ID of the user who created this object.
The ID of the user who updated this object.
The date/time when this object was created.
The date/time when this object was updated.
ID of Message
status
ID of Group
ID of User
ID of Group
ID of a ChatActivityStatusReason, only used when status is "closed"
Additional description of the statusReason. Some ChatActivityStatusReasons require a description.
List of facilities where the patient linked to this chatActivity has appointments.
This date/time changes only when the chat is assigned or the patient gets a messsage. It can be used to sort the chatActivities on screen.
Indicates the last time an unexpected message was sent in the chat. An example is when patient gets an automated appointment reminder requesting to answer YES to confirm or NO to cancel, and patient replies with a completely different message.
Indicates if this chatActivity was created as a consequence of an automated message being sent out, such as an appointment reminder.