Notification message format

Info notification message

Nexconn defines the info notification message (gray bar notification) with ObjectName RC:InfoNtf. Use it to send or insert notifications and tips in a channel.

When sending via the server API, specify the ObjectName and serialize the content JSON into a string for the content field. Built into the client SDK.

Content structure

JSON

{
  "message":"Please be cautious about personal and financial safety during the chat.",
  "extra":""
}

Field	Type	Required	Description
message	String	Yes	Notification content.
extra	String	No	Custom extension data.

Client defaults

• Stored on the client
• Does not count as unread
• Push not supported by default: No preset push content. Provide custom pushContent at send time to trigger push notifications.

Recall notification message

Nexconn defines the recall notification with ObjectName RC:RcNtf. Displayed in the UI after a message is recalled.

Built into the client SDK. Used internally after a recall operation. Not recommended for direct use.

Content structure

Field	Type	Required	Description
operatorId	String	No	User ID of the operator who initiated the recall.
recallTime	Long	Yes	Send time of the original recalled message (milliseconds).
originalObjectName	String	Yes	Message type of the original message.
originalMessageContent	Object	No	Content of the original message.
recallContent	String	No	Content of the recalled text message.
recallActionTime	Long	No	Timestamp when the recall command (RC:RcCmd) was sent (milliseconds).
admin	Boolean	Yes	Whether the recall was performed by an admin.
delete	Boolean	Yes	Whether to delete the original record on mobile clients. false: replace with recall notification. true: delete and hide the notification.
user	Object	No	Sender user info. Recommended for live streaming scenarios only.
extra	String	No	Additional information.

Client defaults

• Stored on the client
• Does not count as unread
• Push not supported by default

Profile change notification message

ObjectName: RC:ProfileNtf. Notifies users of profile changes.

Content structure

JSON

{
  "operation":"Update",
  "data":"{\"nickname\":\"Alice\", \"hometown\":\"beijing\"}",
  "extra":""
}

Field	Type	Required	Description
operation	String	Yes	Profile operation name (user-defined).
data	String	Yes	Operation data.
extra	String	No	Custom extension data.

Client defaults

• Stored on the client
• Does not count as unread
• Push not supported by default

Contact (friend) notification message

ObjectName: RC:ContactNtf. Notifies users of contact/friend operations.

Content structure

JSON

{
  "operation":"Request",
  "sourceUserId":"123",
  "targetUserId":"456",
  "message":"Hi, can we be friends?",
  "extra":""
}

Field	Type	Required	Description
operation	String	Yes	Contact operation. Predefined constants: Request, AcceptResponse, RejectResponse. Extensible by the developer.
sourceUserId	String	Yes	User ID of the notification sender.
targetUserId	String	Yes	For direct channels: recipient user ID. For group/open channels: channel ID.
message	String	Yes	Request or response message (e.g., reason for adding or rejecting).
extra	String	No	Custom extension data.

Client defaults

• Stored on the client
• Does not count as unread
• Push not supported by default

Group notification message

ObjectName: RC:GrpNtf. Notifies users of group operations.

Content structure

JSON

{
  "operatorUserId":"4324",
  "operation":"Rename",
  "data":"Group operation data",
  "message":"Renamed the group to Local Life",
  "extra":""
}

Field	Type	Required	Description
operatorUserId	String	Yes	Operator's user ID.
operation	String	Yes	Operation name (e.g., Create, Rename, Add, Kicked, Quit, Dismiss).
data	String	Yes	Operation data.
message	String	Yes	Message content.
extra	String	No	Custom extension data.

Client defaults

• Stored on the client
• Does not count as unread
• Push not supported by default

Group notification data examples

• Create (operation: "Create"): data contains operatorNickname and targetGroupName.
• Rename (operation: "Rename"): data contains operatorNickname and targetGroupName.
• Add members (operation: "Add"): data contains operatorNickname, targetUserIds, targetUserDisplayNames.
• Remove members (operation: "Kicked"): data contains operatorNickname, targetUserIds, targetUserDisplayNames.
• Quit (operation: "Quit"): data contains operatorNickname, targetUserIds, targetUserDisplayNames, newCreatorId.
• Dismiss (operation: "Dismiss"): data contains operatorNickname.

Command notification message

ObjectName: RC:CmdNtf. Unlike the command message (RC:CmdMsg), this message is stored and displayed in the UI.

Content structure

JSON

{
  "name":"AtPerson",
  "data":"{\"sourceId\":\"9527\"}"
}

Field	Type	Required	Description
name	String	Yes	Command name.
data	String	No	Command data. Accepts any format (e.g., JSON).

Client defaults

• Stored on the client
• Does not count as unread
• Push not supported by default