Struct

Detail description: The external download url of the media message is used for the developer to transparently transmit the media file to other users by filling in this URL when the developer uploads the media file to his own server.

Required or not: If an external URL is sent, this parameter is mandatory on the sender end.

Detail description: The unique ID of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Detail description: The filename of the media file.

Required or not: If you are sending an external URL, you need to fill in this value and include the file extension. If a local file is sent, the value is optional.

Detail description: The size of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Identifies the type of this message.

The unique ID that identifies this message.

Identifies the sending time of a message

Displays the userID of the sender of this message.

Conversation ID. Ids of the same conversation type are unique.

Used to describe whether a message is sent or received.

Describes the sending status of a message.

The type of conversation to which the message belongs.

Indicates the sequence number of the message in the conversation.

The larger the orderKey, the newer the message, and can be used for ordering messages.

SDK locally generated MessageID, developers do not need to pay attention to.

Detail description: Describes whether the message is a message inserted by the developer through [insertMessageToLocalDB].

Default: false.

Describe the receipt status of the message

Business scenario: used to determine the status of the current message in the receipt message

message extension field

The expandable message field visible only on this end can store additional information locally, Through [updateMessageLocalExtendedData] change and currently has a length limit of 128K. If you have special requirements, please contact ZEGO technical support for configuration.

Whether the message is pushed by all employees.

Whether to mention everyone. It can be presented as "@Everyone".

Whether to mention everyone. It can be presented as "@User".

Indicates the sequence number of the message in the conversation.

The number of reply messages corresponding to the root message of the reply message tree.

Information about the source message referenced by the reply message.

The latest editor's userID for this message.

The latest editing timestamp for this message.

Identify if this message is group targeted message.

The last user who pinned this message.

The last timestamp when pinned this message.

Detail description: The external download url of the media message is used for the developer to transparently transmit the media file to other users by filling in this URL when the developer uploads the media file to his own server.

Required or not: If an external URL is sent, this parameter is mandatory on the sender end.

Detail description: The filename of the media file.

Required or not: If you are sending an external URL, you need to fill in this value and include the file extension. If a local file is sent, the value is optional.

Detail description: The size of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Identifies the type of this message.

The content of barrage message.

Identifies the type of this message.

The unique ID that identifies this message.

Identifies the sending time of a message

Displays the userID of the sender of this message.

Conversation ID. Ids of the same conversation type are unique.

Used to describe whether a message is sent or received.

Describes the sending status of a message.

The type of conversation to which the message belongs.

Indicates the sequence number of the message in the conversation.

The larger the orderKey, the newer the message, and can be used for ordering messages.

SDK locally generated MessageID, developers do not need to pay attention to.

Detail description: Describes whether the message is a message inserted by the developer through [insertMessageToLocalDB].

Default: false.

Describe the receipt status of the message

Business scenario: used to determine the status of the current message in the receipt message

message extension field

The expandable message field visible only on this end can store additional information locally, Through [updateMessageLocalExtendedData] change and currently has a length limit of 128K. If you have special requirements, please contact ZEGO technical support for configuration.

Whether the message is pushed by all employees.

Whether to mention everyone. It can be presented as "@Everyone".

Whether to mention everyone. It can be presented as "@User".

Indicates the sequence number of the message in the conversation.

The number of reply messages corresponding to the root message of the reply message tree.

Information about the source message referenced by the reply message.

The latest editor's userID for this message.

The latest editing timestamp for this message.

Identify if this message is group targeted message.

The last user who pinned this message.

The last timestamp when pinned this message.

count.

nextFlag.

Extended field, through which the inviter can carry information to the invitee.

Extended field, through which the inviter can carry information to the invitee.

详情描述: 离线推送配置。 是否必填：非必填。

Extended field, through which the inviter can carry information to the invitee.

Offline push configuration.

Call invite ID.

Call invitation initiator ID.

Call invitation mode.

Call invitation status.

Create a call invitation additional information.

Call invites to create a timestamp.

Call invitation end time.

The list of call member.

Invitee ID.

Extended field, through which the inviter can carry information to the invitee.

The inviter ID of the call invitation.

Extended field, through which the inviter can carry information to the invitee.

The timeout setting of the call invitation, the unit is seconds.

Extended field, through which the inviter can carry information to the invitee.

mode of the call invitation.

The creator of the call invitation is the same as the userID that calls callInvite.

The event stamp when the call invitation was created on the server, accurate to milliseconds.

List of members invited to the call.

The calling party of the current call.

End the call operator.

The pass-through field that comes with invoking the end of the call.

The mode of the call invitation.

Time stamp of the end of the call, in milliseconds. The format is UTC time stamp.

The query number is limited to up to 100.

The flag of the query list.No padding is required for the first query. After the query, callback will return a nextFlag, which can be filled in the next query to continue the query based on the last query.

The timeout setting of the call invitation, the unit is seconds.

Inviter ID.

Extended field, through which the inviter can carry information to the invitee.

mode of the call invitation.

The creator of the call invitation is the same as the userID that calls callInvite.

The event stamp when the call invitation was created on the server, accurate to milliseconds.

List of members invited to the call.

Invitee ID.

Extended field, through which the inviter can carry information to the invitee.

The timeout setting of the call invitation, the unit is seconds.

User id that has not received a call invitation.

User id that has not received a call invitation list.

Call invitation type.

The timeout setting of the call invitation, the unit is seconds. The range is [1, 600].

Extended field, through which the inviter can carry information to the invitee.

Offline push configuration.

Call invitation mode configuration. Supported Version: 2.9.0 or later.

If the pass value is true, the system checks whether the call invitation is delivered in this call and subsequent calls.

Extended field, through which the inviter can carry information to the invitee.

Timestamp of the time when the call invitation was created.

Time stamp of the person join the call invitation.

The pass-through field that comes with invoking the end of the call.

List of user information in the current call invitation.

Extended field, through which the inviter can carry information to the invitee.

Offline push configuration.

Timestamp of the time when the call invitation was created.

Time stamp of the person accepting the call invitation.

The time stamp for me to exit the call.

Additional fields for attaching custom content when sending a reject invitation.

User ID, a string with a maximum length of 32 bytes or less. It is customized by the developer. Only support numbers, English characters and '!', '#', '$', '%', '&', '(', ')', '+', '-', ':', ';', '<', '=', '.', '>', '?', '@', '[', ']', '^', '_', '{', '}', '|', '~'.

user status.

Call the additional information in user information.

List of call members whose status changes.

Error user list.

Offline push configuration.

The title of combine message

The summary of combine message

Combine ID, internal user

List of child messages

Identifies the type of this message.

The unique ID that identifies this message.

Identifies the sending time of a message

Displays the userID of the sender of this message.

Conversation ID. Ids of the same conversation type are unique.

Used to describe whether a message is sent or received.

Describes the sending status of a message.

The type of conversation to which the message belongs.

Indicates the sequence number of the message in the conversation.

The larger the orderKey, the newer the message, and can be used for ordering messages.

SDK locally generated MessageID, developers do not need to pay attention to.

Detail description: Describes whether the message is a message inserted by the developer through [insertMessageToLocalDB].

Default: false.

Describe the receipt status of the message

Business scenario: used to determine the status of the current message in the receipt message

message extension field

The expandable message field visible only on this end can store additional information locally, Through [updateMessageLocalExtendedData] change and currently has a length limit of 128K. If you have special requirements, please contact ZEGO technical support for configuration.

Whether the message is pushed by all employees.

Whether to mention everyone. It can be presented as "@Everyone".

Whether to mention everyone. It can be presented as "@User".

Indicates the sequence number of the message in the conversation.

The number of reply messages corresponding to the root message of the reply message tree.

Information about the source message referenced by the reply message.

The latest editor's userID for this message.

The latest editing timestamp for this message.

Identify if this message is group targeted message.

The last user who pinned this message.

The last timestamp when pinned this message.

The title of combine message

The summary of combine message

Identifies the type of this message.

Pagination token, fill in 0 initially, and then fill in the nextFlag returned from the callback to retrieve data for the next page.

The number of messages that can be retrieved in one search. It is recommended to be less than 20 to reduce performance overhead.

The number of local messages that can be retrieved for a single conversation in one search. It is recommended to be less than 10 to reduce performance overhead.

Search keywords, supports up to 5. Otherwise, an error will occur. For example, if you pass in "1" and "2", the search results will only display conversations that contain both "1" and "2" keywords in the messages.

Message types, can be used to specify message types. Support passing in multiple types.

The subtypes of custom messages have a value range of [0,200]. Developers can use this range to search for specific custom types.

Send user ID, supports up to 5. For example, if you pass in "zego2023", the search results will only display conversations where messages have been sent by the user "zego2023".

The starting point of the search, in milliseconds, with a default value of 0. The format is UTC timestamp.

The ending point of the search, which must be greater than the startTime, in milliseconds. The default value is 0 and the format is UTC timestamp.

The conversation ID of the local message to be search.

conversation type.

Total message count

Search results of messages.

Number of sessions that were deleted.

User ID, a string with a maximum length of 32 bytes or less. It is customized by the developer. Only support numbers, English characters and '!', '#', '$', '%', '&', '(', ')', '+', '-', ':', ';', '<', '=', '.', '>', '?', '@', '[', ']', '^', '_', '{', '}', '|', '~'.

Description Reason for the query failure.

Expiration stamp of cache cleanup.

Total file size in bytes (B).

Example Query the expiration timestamp of the cache.

Detail description: The external download url of the media message is used for the developer to transparently transmit the media file to other users by filling in this URL when the developer uploads the media file to his own server.

Required or not: If an external URL is sent, this parameter is mandatory on the sender end.

Detail description: The unique ID of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Detail description: The filename of the media file.

Required or not: If you are sending an external URL, you need to fill in this value and include the file extension. If a local file is sent, the value is optional.

Detail description: The size of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Identifies the type of this message.

The unique ID that identifies this message.

Identifies the sending time of a message

Displays the userID of the sender of this message.

Conversation ID. Ids of the same conversation type are unique.

Used to describe whether a message is sent or received.

Describes the sending status of a message.

The type of conversation to which the message belongs.

Indicates the sequence number of the message in the conversation.

The larger the orderKey, the newer the message, and can be used for ordering messages.

SDK locally generated MessageID, developers do not need to pay attention to.

Detail description: Describes whether the message is a message inserted by the developer through [insertMessageToLocalDB].

Default: false.

Describe the receipt status of the message

Business scenario: used to determine the status of the current message in the receipt message

message extension field

The expandable message field visible only on this end can store additional information locally, Through [updateMessageLocalExtendedData] change and currently has a length limit of 128K. If you have special requirements, please contact ZEGO technical support for configuration.

Whether the message is pushed by all employees.

Whether to mention everyone. It can be presented as "@Everyone".

Whether to mention everyone. It can be presented as "@User".

Indicates the sequence number of the message in the conversation.

The number of reply messages corresponding to the root message of the reply message tree.

Information about the source message referenced by the reply message.

The latest editor's userID for this message.

The latest editing timestamp for this message.

Identify if this message is group targeted message.

The last user who pinned this message.

The last timestamp when pinned this message.

Detail description: The external download url of the media message is used for the developer to transparently transmit the media file to other users by filling in this URL when the developer uploads the media file to his own server.

Required or not: If an external URL is sent, this parameter is mandatory on the sender end.

Detail description: The filename of the media file.

Required or not: If you are sending an external URL, you need to fill in this value and include the file extension. If a local file is sent, the value is optional.

Detail description: The size of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Identifies the type of this message.

Add a friend postscript.

Alias of friend.

Friend attributes. Up to 5 can be set. The key of the attribute can only be selected from k0 to k4.

friend alias.

friend attributes.

Offline push configuration

Detail description: If you are the applicant, here is the respondent information; if you are the respondent, here is the applicant information;

The wording of friend application information.

Friend add time.

Friend application status update time.

Friend application type.

Friend application state.

Total number of current queries.

The index of the current query anchor point.

Offline push configuration

Add a friend postscript.

Alias of friend.

Friend attributes. Up to 5 can be set. The key of the attribute can only be selected from k0 to k4.

Offline push configuration.

Delete type.

Detail description: UserID of the operator.

The alias of friend.

Friend attributes. Up to 5 can be set. The key of the attribute can only be selected from k0 to k4.

Friend add time.

User name, defined by you. For version 2.0.0 and onwards, the string has a maximum length of 256 bytes.

The user avatar, which is custom generated by the developer, is not restricted by special characters and has a maximum length of 500 bytes.

Extended field information of the user.

Total number of current queries.

The index of the current query anchor point.

Check type.

user ID.

Friend relationship type.

Search keyword list.

Whether to match friend aliases.

Current total number of searches.

The starting and ending index of the current search.

basic group information.

group message notification status.

the group alias defined by user, which is visible only to that user.

Group properties, up to 10 can be configured..

group notice.

The maximum number of group members.

Verification mode for joining the group.

Verification mode for invite to the group.

Verification mode for being invited to the group.

Detail description: The applicant is the applicant when applying to join, the invitee when applying to invite, and the inviter when applying by invitation.

The wording of group application information.

Group application create time.

Group application status update time.

Group application type.

Group application state.

Group information for applying to join the group.

The operator who agrees to join the group application.

count. It is advised to be no more than 30.

nextFlag.

Group attribute update action.

group properties.

The expiration date of the group gag.

Whether the group session is unavailable.

conversationID.

conversationName is the same as the groupName/userName value corresponding to the session.

conversation type.

Session unread.

last message.

OrderKey is used to describe the order of messages in the session. The larger orderKey is, the newer it is.

session notification status.

Detail description: Conversation avatar URL. The peer to peer chat conversation avatar URL is the same as the user avatar URL, and the group chat conversation avatar URL is the same as the group avatar URL.

Use Limit: the maximum number of characters is 500 bytes. There is no limit on special characters.

Whether the conversation is pinned.

When reminded in a message or reminded to everyone in a conversation, this array will record the reminders.

After the friend remarks are set through [updateFriendAlias], this parameter is changed for each chat conversation. After setting a group alias by [updateGroupAlias], the corresponding group chat conversation's parameter will be modified synchronously.

Describes all the existing marks for the conversation.

Conversation draft, when draft set conversation will carry this parameter.

Group entry type.

The timestamp of the server when joining the group.

The operator who agrees to the application to join the group or the inviter who invites the application to join the group.

basic group information.

group properties.

Group of announcement.

group message notification status.

Group mute info.

The timestamp of the server when the group was created.

The maximum number of group members.

Verification mode for joining the group.

the group alias defined by user, which is visible only to that user.

groupID.

Required or not: Mandatory, it will be automatically generated in the background.

Value: Supports only digits, English characters, and '!', '#', '$', '%', '&', '(', ')', '+', '-', ':', ';', '<', '=', '.', '>', '?', '@', '[', ']', '^', '_', '{', '}', '|', '~' and not by '#' at the beginning.

Group name.

Offline push configuration.

Offline push configuration.

Postscript to the application operation.

Offline push configuration.

Offline push configuration.

Offline push configuration.

Postscript to the application operation.

Offline push configuration.

Group member nickname.

group role.

Detailed description: group member avatar URL.

User Limit: the maximum number of characters is 500 bytes. There is no limit on special characters.

Group member's mute expiration time. When it's 0, it means no mute; when it's -1, it means permanent mute.

Information about group members when they join the group.

User ID, a string with a maximum length of 32 bytes or less. It is customized by the developer. Only support numbers, English characters and '!', '#', '$', '%', '&', '(', ')', '+', '-', ':', ';', '<', '=', '.', '>', '?', '@', '[', ']', '^', '_', '{', '}', '|', '~'.

User name, defined by you. For version 2.0.0 and onwards, the string has a maximum length of 256 bytes.

The user avatar, which is custom generated by the developer, is not restricted by special characters and has a maximum length of 500 bytes.

Extended field information of the user.

Group members mute duration, the unit is seconds. The value is -1, which means permanent mute. If you need to implement non-permanent mute, the upper limit is 604800 (7 days). If you need to increase it, please contact ZEGO technical support.

count.

nextFlag.

count. Quantity, upper limit is 100, over 100 will be treated as 100.

nextFlag.

count.

The flag for querying, fill in 0 when calling the interface for the first time. When calling the interface again later, fill in the nextFlag returned from the callback to retrieve the remaining data.

Search keywords, up to 5 keywords are supported, otherwise an error will be reported. For example: passing in "1" and "2" will make the search results only show group members whose names contain both keywords "1" and "2".

Whether the search scope includes group member user nickname. Default is false.

Group member nickname.

group role.

User ID, a string with a maximum length of 32 bytes or less. It is customized by the developer. Only support numbers, English characters and '!', '#', '$', '%', '&', '(', ')', '+', '-', ':', ';', '<', '=', '.', '>', '?', '@', '[', ']', '^', '_', '{', '}', '|', '~'.

User name, defined by you. For version 2.0.0 and onwards, the string has a maximum length of 256 bytes.

The user avatar, which is custom generated by the developer, is not restricted by special characters and has a maximum length of 500 bytes.

Extended field information of the user.

Detailed description: The next sign. Initially fill in 0, then get the next next flag from the [ZIMGroupMessageReceiptMemberListQueriedCallback] callback.

Group mute mode.

Group mute duration, the unit is seconds. The value is -1, which means permanent mute. If you need to implement non-permanent mute, the upper limit is 604800 (7 days). If you need to increase it, please contact ZEGO technical support.

Group role list.

Group mute mode.

Group mute expiration time, measured in seconds. When it's 0, there is no mute; when it's -1, it means permanent mute.

Detail description: Role list muted in the group.

Group member information.

The operator's user ID.

The operator's username.

The operator's group member nickname.

The operator's group member role.

count.

The flag used to search groups.

Search keywords. For example: passing in "1" and "2" will make the search results only show groups whose group names contain both keywords "1" and "2".

Whether the search scope includes group member user nicknames. Default is false.

Whether the search scope includes group member user names. Default is false.

group info.

Group member information

Verification mode for joining the group.

Verification mode for invite to the group.

Verification mode for being invited to the group.

Detailed description: The thumbnail local path of the image file.

Required or not: The sender does not need to fill in it. After calling [downloadMediaFile] to download, the SDK will generate this value.

Detail description: Thumbnail external download URL of the image file. When developers upload thumbnails to their own servers, the SDK can pass through this field to other users.

Required or not: optional on the sender side, this field will only take effect when fileDownloadUrl is filled in.

Detailed description: The large image local path of the image file.

Required or not: The sender does not need to fill in it. After calling [downloadMediaFile] to download, the SDK will generate this value.

Detail description: large Image external download URL of the image file. When developers upload large Images to their own servers, the SDK can pass through this field to other users.

Required or not: optional on the sender side, this field will only take effect when fileDownloadUrl is filled in.

Original image width.

Original image height.

Large image width. When sending local images, the ZIM service will compress the shortest side of the original image to 720 pixels, with the other side being scaled proportionally. When the shortest side of the original image is less than 720 pixels, no compression is applied.

Large image height. When sending local images, the ZIM service will compress the shortest side of the original image to 720 pixels, with the other side being scaled proportionally. When the shortest side of the original image is less than 720 pixels, no compression is applied.

Thumbnail width. When sending local images, the ZIM service will compress the shortest side of the original image to 198 pixels, with proportional scaling applied to the other side. If the shortest side of the original image is smaller than 198 pixels, no compression will be performed.

Thumbnail height. When sending local images, the ZIM service will compress the shortest side of the original image to 198 pixels, with proportional scaling applied to the other side. If the shortest side of the original image is smaller than 198 pixels, no compression will be performed.

Detail description: The external download url of the media message is used for the developer to transparently transmit the media file to other users by filling in this URL when the developer uploads the media file to his own server.

Required or not: If an external URL is sent, this parameter is mandatory on the sender end.

Detail description: The unique ID of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Detail description: The filename of the media file.

Required or not: If you are sending an external URL, you need to fill in this value and include the file extension. If a local file is sent, the value is optional.

Detail description: The size of the media file.

Required or not: The sender does not need to fill in, this value is generated by the SDK.

Identifies the type of this message.

The unique ID that identifies this message.

Identifies the sending time of a message

Displays the userID of the sender of this message.

Conversation ID. Ids of the same conversation type are unique.

Used to describe whether a message is sent or received.

Describes the sending status of a message.

The type of conversation to which the message belongs.

Indicates the sequence number of the message in the conversation.

The larger the orderKey, the newer the message, and can be used for ordering messages.

SDK locally generated MessageID, developers do not need to pay attention to.

Detail description: Describes whether the message is a message inserted by the developer through [insertMessageToLocalDB].

Default: false.

Describe the receipt status of the message

Business scenario: used to determine the status of the current message in the receipt message

message extension field

The expandable message field visible only on this end can store additional information locally, Through [updateMessageLocalExtendedData] change and currently has a length limit of 128K. If you have special requirements, please contact ZEGO technical support for configuration.

Whether the message is pushed by all employees.

Whether to mention everyone. It can be presented as "@Everyone".