Skip to main content

Starting March 27, 2026, RC is rebranded as Nexconn. Existing RC SDK customers can continue using this documentation. New customers should refer to the Nexconn developer documentation.

Set Do Not Disturb for Specified Conversation Types

Set the Do Not Disturb logic for specified conversation types for a specific user (requestId). Supported conversation types include: one-to-one chat, group chat, ultra group, and system conversation. After setting, the SDK can obtain the latest conversation Do Not Disturb status information in real time.

tip
  • The current setting is at the user level. The Do Not Disturb logic set by the user for "conversation types" has a lower priority than the Do Not Disturb logic set for "specified conversations." For details, see Set Do Not Disturb for Specified Conversations.

Request Method

POST: https://data center domain/conversation/type/notification/set.json

Rate Limit: 100 requests per second

Signature Rule: All server API requests require signature verification. For details, see API Request Signature.

Body Parameters

The HTTP request body data format is application/x-www-form-urlencoded, and the following HTTP form parameters are supported:

ParameterTypeRequiredDescription
conversationTypeStringYesConversation type. Supported conversation types include: 1 (one-to-one chat), 3 (group chat), 6 (system conversation), 10 (ultra group chat).
requestIdStringYesThe user ID for which the Do Not Disturb setting is applied.
unpushLevelIntYes
  • -1: Notify for all messages
  • 0: Not set (if the user has not set this, the default setting at the group or APP level will apply. If no default is set, all messages will be notified.)
  • 1: Notify only for @ mentions
  • 2: Notify only for @ mentions of specified users

    For example: @张三 will notify Zhang San, but @所有人 will not notify anyone.

  • 4: Notify only for @ mentions of all group members, only receiving notifications for @所有人.
  • 5: Do not receive notifications

Request Example

POST /conversation/type/notification/set.json HTTP/1.1
Host: api.rong-api.com
App-Key: uwd1c0sxdlx2
Nonce: 14314
Timestamp: 1408710653491
Signature: 45beb7cc7307889a8e711219a47b7cf6a5b000e8
Content-Type: application/x-www-form-urlencoded

conversationType=1&requestId=b5NwvIrW8&unpushLevel=2

Response

The HTTP response body contains a JSON object with the following structure:

Return ValueTypeDescription
codeNumberReturn code, 200 indicates success.

Response Example

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{"code":200}