Skip to main content

Message Management Service Configuration

Features​

The following configurations related to message management functions of the Server API are available in the Chat settings page in the RC Console:

  • Sensitive Word Filtering for Messages Sent via Server API: Controls whether the sensitive word mechanism is enabled for messages sent via the Server API. You can enable this in the RC Console under Chat > Chat settings > Security & Moderation.
  • Real-time Routing for Messages Sent via Server API: When enabled, messages sent via the Server API will also undergo post-messaging callback. This only takes effect if the Post-messaging Callback is already activated. You can enable this in the RC Console under Chat > Chat settings.
  • Historical Message Log Download via Server API: The IM service can save historical message records of all conversations within the APP. Historical message records are provided in the form of log files, which are compressed. You can use the Server API to obtain the historical message logs for a specified App. Note that the Server API interface only returns the download link for the message record file. After obtaining the link, you need to download it yourself.

Enable Services​

Visit the Chat settings page in the RC Console to enable the above features.

Additional Message Management Services​

The following configurations related to message management functions of the Server API are available in the Chat settings page in the RC Console:

  • Post-messaging Callback: The Post-messaging Callback supports synchronizing message data from one-to-one chats, groups, ultra groups, and chatrooms to the designated application server. When activating the service, you need to configure a callback receiving address that is accessible. You can enable this service in the RC Console under Chat > Chat settings. Note:
    • To enable post-messaging callback for ultra group message extensions, please submit a ticket.
    • To enable post-messaging callback for messages containing blocked sensitive words, please submit a ticket to apply for activation.
    • To enable post-messaging callback for status messages sent by the client, please submit a ticket to apply for the One-to-One Status Message Routing Function. If you need to enable post-messaging callback for any messages sent via the Send One-to-One Status Message or Send Group Status Message interfaces, you need to activate the Real-time Routing for Messages Sent via Server API service.
    • To enable post-messaging callback for ultra group message extension changes, please submit a ticket to apply for adjusting Whether Ultra Group Message Extensions Are Routed. After activating the service, if the ultra group message extensions are changed, the server will generate a message of type RC:MsgExMsg. The new message is only used for message routing synchronization and will not be synchronized to the client SDK. The new message ID is generated by the server, and the originalMsgUID field will carry the MsgUID of the original message. Note that the extension data carried when the message is sent cannot be obtained through post-messaging callback.
  • Cloud Storage for One-to-One and Group Messages: The Cloud Storage for One-to-One and Group Messages service is enabled by default. Historical messages for one-to-one chats, group chats, and system conversations are stored on RC's server for client-side historical message retrieval.
  • Multi-Device Message Synchronization: Enables message synchronization between multiple devices under the same user account. If you need to synchronize messages sent via the Server API to the offline client of the sender, it is recommended to enable this feature. You can enable this service in the RC Console under Chat > Chat settings.

Modify Service Configuration​

Visit the Chat settings page in the RC Console to enable the above services. In the development environment, these services can be used for free. In production environments, these services are available for Chat Starter Plan or Chat Pro Plan. Specific features and fees are subject to the Billing Instructions document.

Last updated on