Transient message format

Transient messages are not stored on the client and do not count toward the unread message count.

tip

Do not confuse transient message types with the server API for sending transient messages:

• Transient message types: Not stored on the client. Not counted as unread. Can be sent from clients (typically by the SDK internally) or via the server API.
• Send transient message API: Accepts any built-in message type. If the recipient is offline, the message is not delivered.

Typing status message

Nexconn defines the typing status message with ObjectName RC:TypSts.

When sending via the server API, specify the ObjectName and serialize the content JSON object into a string for the content field. The client SDK has this message type built in. The client does not store this message and does not count it as unread.

• If the typing indicator feature is enabled in the client SDK, the SDK automatically sends this message in direct channels. Group channels do not support automatic typing indicator messages.
• To send via the server API, use the transient message endpoints.

Content structure

JSON

{
  "typingContentType":"RC:TxtMsg"
}

Field	Type	Required	Description
typingContentType	String	Yes	The message type currently being typed.

Client defaults

• Not stored on the client
• Does not count as unread
• Push notifications not supported