Messaging

This section highlights the steps you will need to follow to begin integrating chat messaging into your products

The message payload is always the same regardless of which Development Kit the user is using. Users also have a choice on what type of message they want to send.‌

Message Description

Name	Data Type	Description	Attributes
messageId	string	The id of this message	​Content
parentId	string	The messageId of the parent of this message	​Content
childrenNumber	integer	The number of messages with parentId of this message	​Content
channelId	string	The name of the channel this message was created in	​Content
userId	string	The name of the user this message was created by	​Content
type	string	The message type	enum*: text custom image file
tags	Array.<string>	The message tags	​Content
data	Object	The message data (any text will be stored in text key)	text: Text message
isDeleted	boolean	The message has been marked as deleted	​Content
createdAt	date	The date/time the message was created at	​Content
updatedAt	date	The date/time the message was updated at	​Content
editedAt	date	The date/time the message was edited at	​Content
flagCount	integer	The number of users that have flagged this message	​Content
reactions	Object	The reaction data (stored as a reactionName and counter key/value pair)	Example: { like: 1, dislike: 2 }
reactionsCount	integer	The total number of reactions on this message	​Content
myReactions	Array.<string>	A list of user's reactions on this message	​Content

Messages are JSON content containers that can have up to 20,000 characters or can weigh up to 100KB for custom messages. They will be synchronized among all channel users in real-time. If a message requires larger binary data (such as when sending files), we recommend to upload the data to another cloud storage service, such as AWS S3, and store the URL to the content in the message data.

In addition to the JSON message type, the SDK also provides support for common text and image message types. These additional types are built on top of the standard JSON message layer.

In case of image messages, the SDK freely provides a cloud storage service that will process and store all images uploaded: you don't need to set up and manage a separate cloud storage service for this common case.

All messaging methods are contained in a AmityMessageRepository class. Before calling any messaging methods, you must ensure to first instantiate a repository instance using the AmityClient instance you created on setup.

let messageRepository = AmityMessageRepository(client: client)

Refer to the following sections for a more detailed discussion on tasks related to messages:

• Creating messages

• Viewing messages

• Message reaction

• Replying to messages

• Editing messages

• Mention in messages

• Deleting messages

• Querying messages

• Filtering messages