the bookmark extension field that can contain 1024 characters
The specific data of the bookmark, the maximum number of characters is 20480
Type, you can customize the mapping relationship, must be an integer
Unique ID.
Note: When the uniqueId is passed,the server checks whether there is a collection record before for uniqueId. If it does not exist, a new collection will be added, and if it exists, the collection will be updated.
Collection
Add a PIN tag to a message. If successful, the onPinMsgChange callback of the multi-device login device will be triggered
The structure of pinned messages
the extension field of PIN messages
Add a quick comment
Custom text for push notifications
Comment
Note: Enter an integer, you can create custom mapping rules. For example, 1 for the like emoj, 2 for the clapping emoj.
Extension
Message to be replied
Whether message count is required (badge at the app corner). The default value is false.
whether a push notification is required. The default value is false..
Custom property of a push notification in JSON.
Title for a push notification
Comment
Quick comment
Extension
ID of the account making the comment.
time when the comment is posted.
Messaging scenario:
account of a sender
The ID used by the server to distinguish messages, used to get message history and keywords for searching message history.
Note: This field may not be available. For example, the message is filtered by anti-spam.
Messaging scenario:
Timestamp
ID of a recipient, account ID or group ID
Delete multiple collections at a time.
List of collections to be deleted, up to 100
List of collections to be deleted
Number of deleted collections
Remove the PIN tag from messages The onPinMsgChange callback is triggered for synchronization across devices.
The structure of pinned messages
Delete a quick comment
Custom text for push notifications
Comment
Note: Enter an integer, you can create custom mapping rules. For example, 1 for the like emoj, 2 for the clapping emoj.
Extension
Message to be replied
Whether message count is required (badge at the app corner). The default value is false.
whether a push notification is required. The default value is false..
Custom property of a push notification in JSON.
Title for a push notification
Comment
Quick comment
Extension
ID of the account making the comment.
time when the comment is posted.
Message, extract several fields in the NIMMessage structure, and idServer must exist.
account of a sender
The ID used by the server to distinguish messages, used to get message history and keywords for searching message history.
Note: This field may not be available. For example, the message is filtered by anti-spam.
Messaging scenario:
Timestamp
ID of a recipient, account ID or group ID
Query collections
Timestamp of start time in milliseconds, default value: 0
Timestamp of the end time in milliseconds. the default value is the current server time
The ID of the last collection in the last query
Note: It is recommended to fill out from the second page, so that the server can distinguish two records with the same timestamp.
The upper limit of messages per query. 100 messages by default
Sorting order. The default value is false
Type, you can customize the mapping relationship, must be an integer. All types of messages are queried by default.
List of collections
Total number of collections
Get all PIN messages by conversation ID
session ID
session ID
Query message history by message ID and other information, exclusive to thread chat
Query messages by idServer. for messages in a thread The maximum length of the parameter array is 100.
Get multiple quick comments at a time.
Message to be replied
The recent update time of a quick comment.
Comment
idClient of a message commented
idServer of a message commented
Get the list of messages in a thread.
Start time in milliseconds. the default value: 0
Timestamp of the end time in milliseconds, the default value is the current time of the server
The idServer of the last message in the last query. No value for the first query.
The upper limit of messages per query. 100 messages by default
The default false means to search for message history forward from endTime, and true means to search for message history backward from beginTime
Scenario
Sender account of a message in the thread
ServerID of the root message in a thread.
Time of the root message in a thread
Recipient of a thread message
List of relevant messages
root message in a thread
Get the timestamp.
Total number of messages
Update collections, only custom fields can be updated.
Collection object. Only the custom field can be updated, and you can use the new custom field into this object.
Note: to delete the custom field, pass the object without the custom field.
Update PIN messages. The onPinMsgChange callback is triggered for synchronization across devices.
Note: Only extension fields can be updated
The structure of pinned messages
the extension field of PIN messages
Add collection, and the content of the collections determined according to the business scenario. Collections are only visible to the current user.