Overview
Chat messages enable communication between tourists and guides within chat threads. Messages support different types (text, system, file) and track delivery and read status.Create Chat Message
Request Body
The ID of the chat thread this message belongs to
The user ID of the message sender
The content of the message
Type of message. Valid values:
TEXT, SYSTEM, FILETimestamp when the message was sent in ISO 8601 format (e.g.,
2026-03-11T14:35:00)Timestamp when the message was read in ISO 8601 format. Null if unread.
Response
Unique identifier for the message
The chat thread ID this message belongs to
The sender’s user ID
The message content
Message type (
TEXT, SYSTEM, or FILE)Timestamp when the message was sent
Timestamp when the message was read (null if unread)
Get All Chat Messages
Response
Returns an array of chat message objects.Get Chat Message by ID
Path Parameters
The unique identifier of the chat message
Response
Update Chat Message
readAt timestamp.
Path Parameters
The unique identifier of the chat message to update
Request Body
The ID of the chat thread this message belongs to
The user ID of the message sender
The content of the message
Type of message. Valid values:
TEXT, SYSTEM, FILETimestamp when the message was sent in ISO 8601 format
Timestamp when the message was read in ISO 8601 format. Set this to mark a message as read.
Response
Delete Chat Message
Path Parameters
The unique identifier of the chat message to delete
Response
Returns a success status code (typically 204 No Content) if the deletion was successful.Message Types
Chat messages can have one of the following types:- TEXT: Standard text message sent by users
- SYSTEM: Automated system message (e.g., “Booking confirmed”, “Tour started”)
- FILE: Message containing a file attachment
Read Status
Messages track their read status through thereadAt field:
- Unread:
readAtisnull - Read:
readAtcontains the timestamp when the message was read
readAt field.
Related Endpoints
- Chat Threads - Manage chat threads that contain messages