Server APIs

Generating UserSig
RESTful APIs
- RESTful API Overview
- RESTful API List
- Message Related
  - Send Message
    - Sending One-to-One Messages to One User
    - Sending One-to-One Messages to Multiple Users
    - Sending Ordinary Messages in a Group
    - Sending System Messages in a Group
    - Broadcast Message of Audio-Video Group
    - Importing One-to-One Messages
    - Importing Group Messages
  - Historical Message
    - Modifying Historical One-to-one Messages
    - Modifying Historical Group Messages
    - Pulling Historical One-to-one Messages
    - Pulling Historical Group Messages
  - Delete Message
    - Deleting Messages Sent by a Specified User
  - Withdraw Message
    - Recalling One-to-One Messages
    - Recalling Group Messages
  - Read Receipt
    - Marking One-to-One Messages as Read
    - Pulling Group Message Read Receipt Details
    - Pulling Read Receipts for Group Messages
  - Message Extension
    - Pulling the Message Extension of a One-to-One Message
    - Configuring Message Extension for a One-to-One Message
    - Pulling Message Extension of a Group Message
    - Configuring Message Extension for a Group Message
  - Pushing to All Users
    - API for Pushing to All Users
    - Pushing to All Users
    - Setting Application Attribute Names
    - Getting Application Attribute Names
    - Getting User Attributes
    - Setting User Attributes
    - Deleting User Attributes
    - Getting User Tags
    - Adding User Tags
    - Deleting User Tags
    - Deleting All Tags of a User
- Session Related
  - Conversation List
    - Pulling a conversation list
  - Session Unread Count
    - Setting the Unread Message Count of a Member
    - Querying Unread One-to-One Message Count
  - Delete Session
    - Deleting a conversation
  - Session Grouping Tag
    - Creating Conversation Group Data
    - Updating Conversation Group Data
    - Deleting Conversation Group Data
    - Creating or Updating Conversation Mark Data
    - Searching for Conversation Group Marks
    - Pulling Conversation Group Mark Data
- Group Related
  - Group Management
    - Getting All Groups in an App
    - Creating a Group
    - Disbanding a Group
    - Getting the Groups a User Has Joined
  - Group Information
    - Getting Group Profiles
    - Modifying the Profile of a Group
    - Importing a Group Profile
  - Group Member Management
    - Adding Group Members
    - Deleting Group Members
    - Banning Group Members
    - Unbanning Group Members
    - Bulk Muting and Unmuting
    - Getting the List of Muted Group Members
    - Changing Group Owner
    - Querying the Roles of Users in a Group
    - Importing Group Members
  - Group Member Information
    - Getting Group Member Profiles
    - Modifying the Profile of a Group Member
  - Group Custom Attributes
    - Getting Group Custom Attributes
    - Modifying Group Custom Attributes
    - Clearing Group Custom Attributes
    - Resetting Group Custom Attributes
    - Deleting Group Custom Attributes
  - Live Group Management
    - Getting the Number of Online Users in an Audio-Video Group
    - Getting the List of Online Members in Audio-Video Group
    - Setting Audio-Video Group Member Marks
    - Getting the List of Banned Group Members.
  - Community Management
    - Creating Topic
    - Deleting Topic
    - Getting Topic Profile
    - Modifying Topic Profile
    - Importing Topic Profiles
  - Group Counter
    - Getting Group Counters
    - Updating Group Counters
    - Deleting Group Counters
- User Management
  - Account Management
    - Importing a Single Account
    - Importing Multiple Accounts
    - Deleting Accounts
    - Querying Accounts
  - User Information
    - Setting Profiles
    - Pulling Profiles
  - User Status
    - Invalidating Account Login States
    - Querying Account Online Status
  - Friend Management
    - Adding Friends
    - Importing Friends
    - Updating Friends
    - Deleting Friends
    - Deleting All Friends
    - Verifying Friends
    - Pulling Friends
    - Pulling Specified Friends
  - Friend Lists
    - Adding Lists
    - Deleting Lists
    - Pulling Lists
  - Blocklist
    - Blocklisting Users
    - Unblocklisting Users
    - Pulling a Blacklist
    - Verifying Users on a Blocklist
- Global Mute Management
  - Setting Global Mute
  - Querying Global Mute
- Operations Management
  - Pulling Operations Data
  - Downloading Recent Messages
  - Getting Server IP Addresses
- Chatbots
  - Pulling Chatbot Accounts
  - Creating Chatbot Accounts
  - Deleting Chatbot Accounts
Webhooks
- Webhook Overview
- Webhook Command List
- Operations Management Callbacks
  - API Overclocking Alarm Callbacks
- Online Status Webhooks
  - Status Change Webhooks
- Relationship Chain Webhooks
  - After a Profile Is Updated
  - Before a Friend Is Added
  - Before a Friend Request Is Responded
  - After a Friend Is Added
  - After a Friend Is Deleted
  - After a User Is Added to Blocklist
  - After a User Is Removed from Blocklist
- One-to-One Message Webhooks
  - Before a One-to-One Message Is Sent
  - After a One-to-One Message Is Sent
  - After a One-to-One message Is Marked as Read
  - After A One-to-One Message Is Recalled
- Group Webhooks
  - Before a Group Is Created
  - After a Group Is Created
  - Before Applying to Join a Group
  - Before Inviting a User to a Group
  - After a User Joins a Group
  - After a User Leaves a Group
  - Before Group Message Is Sent
  - After a Group Message Is Sent
  - After a Group Is Full
  - After a Group Is Disbanded
  - After Group Profile Is Modified
  - Callback After Recalling Group Messages
  - Webhook for Online and Offline Status of Audio-Video Group Members
  - Webhook for Exceptions When Group Messages Are Sent
  - Before a Topic Is Created
  - After a Topic Is Created
  - After a Topic Is Deleted
  - Topic Profile Change Webhook
  - Callback After Group Member Profile Changed
  - Callback After Group Attribute Changed
  - Callback After Read Receipt
  - Callback After the Group Owner Changed
- Webhook Mutual Authentication Configuration Guide
  - Apache Mutual Authentication Configuration
  - Nginx Mutual Authentication Configuration
- Chatbot webhooks
  - Chatbot Passthrough Message Callback

Before a One-to-One Message Is Sent

Overview
This webhook is used by the app backend to manage users' one-to-one messages in real time, including:
Records one-to-one messages sent in real time, for example, by recording a log or synchronizing the messages to other systems.
Blocks users' requests to send non-compliant messages of any type, such as text, image, and custom messages.
Note: 
 The timeout period of the webhook before message sending is two seconds by default, and we recommend you not adjust it. This webhook may time out when used for text moderation.
Limits
To enable this webhook, you must configure the webhook URL and enable the corresponding switch for this webhook. For more information on the configuration method, see Webhook Configuration.
During this webhook event, the Chat backend initiates an HTTPS POST request to the app backend.
After receiving the webhook request, the app backend must check whether the SDKAppID contained in the request URL is the SDKAppID of the app.
If the webhook before sending one-to-one messages and the webhook after sending one-to-one messages are both enabled and forbidding message sending is returned for the webhook before sending one-to-one messages, the webhook after sending one-to-one messages cannot be triggered.
If the webhook before sending one-to-one messages and the webhook after sending one-to-one messages are both enabled and the message body is modified during the webhook before sending one-to-one messages, the webhook after sending one-to-one messages will use the modified message for webhook.
For more security considerations, see the Security Considerations section in Webhook Overview.
Webhook Triggering Scenarios
An app user sends a one-to-one message on the client.
The app admin sends a one-to-one message by calling the sendmsg RESTful API.
Webhook Triggering Timing
The Chat backend has received a one-to-one message sent by a user but has not delivered the message to the target user.
API Calling Description
Sample request URL
In the following sample, the webhook URL configured in the app is https://www.example.com.
Example:
https://www.example.com?SdkAppid=$SDKAppID&CallbackCommand=$CallbackCommand&contenttype=json&ClientIP=$ClientIP&OptPlatform=$OptPlatform
Request parameters
Parameter
Description
https
The request protocol is HTTPS, and the request method is POST.
[www.example.com](http://www.example.com)
Callback URL
SdkAppid
The SDKAppID assigned by the Chat console when the app is created
CallbackCommand
The value is always C2C.CallbackBeforeSendMsg.
contenttype
Always json
ClientIP
Client IP, such as 127.0.0.1
OptPlatform
Client platform. For valid values, see the description of OptPlatform in the Webhook Protocols section of Webhook Overview.
Sample requests
{
    "CallbackCommand": "C2C.CallbackBeforeSendMsg", // Webhook command
    "From_Account": "jared", // Sender
    "To_Account": "John", // Recipient
    "MsgSeq": 48374, // Sequence number of the message
    "MsgRandom": 2837546, // Random number of the message
    "MsgTime": 1557481126, // Timestamp in seconds indicating when the message is sent 
    "MsgKey": "48374_2837546_1557481126", // Unique identifier of the message. It can be used to recall the message via a RESTful API call.
    "OnlineOnlyFlag":1, // The value is `1` if it is an online message and `0` if it's not
    "MsgBody": [ // Message body. For more information, see the `TIMMessage` message object.
        {
            "MsgType": "TIMTextElem", // Text
            "MsgContent":{
                "Text": "red packet"
            }
        }
    ],
    "CloudCustomData": "your cloud custom data"
}
Request fields
Field
Type
Description
CallbackCommand
String
Webhook command
From_Account
String
UserID of the message sender
To_Account
String
UserID of the message recipient
MsgSeq
Integer
Sequence number of the message. It is used to identify the message and the value is a random 32-bit unsigned integer.
MsgRandom
Integer
Random number of the message. It is used to identify the message and the value is a random 32-bit unsigned integer.
MsgTime
Integer
Timestamp in seconds indicating when the message is sent.
One-to-one messages are preferentially sorted by MsgTime. 
Messages sent in the same second are sorted by MsgSeq. 
Messages with larger values of MsgSeq are after those with smaller values.
MsgKey
String
Unique identifier of the message. It can be used to recall the message via a RESTful API call.
OnlineOnlyFlag
Integer
The value is 1 if it is an online message and 0 if it's not.
MsgBody
Array
Message body. For more information, see Message Formats.
CloudCustomData
String
Custom message data. It is saved in the cloud and will be sent to the receiver. Such data can be pulled after the app is uninstalled and reinstalled.
Sample response when sending messages is allowed
The user is allowed to send group messages, and the content of the message is not modified.
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 0 // `0` indicates the user is allowed to send messages.
}
Sample response when sending messages is forbidden
The user is not allowed to send group messages. In this case, the message is not sent, and the error code 20006 is returned to the user (message sender).
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 1 // `1` indicates that the user is not allowed to send messages.
}
Sample response when messages are discarded silently
The user is not allowed to send group messages. In this case, the message is not sent, but a success message will be returned to the sender.
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 2 // The value `2` indicates the message is silently discarded.
}
Sample response when the message content is modified
In the following sample, the message sent by the user is modified (a custom message or custom message data is added), and the Chat backend will send the modified message. With this feature, the app backend can add special content, such as the user level and title, to the message sent by the user.
Example:
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 0, // This field must be set to `0` so that the modified message can be sent normally.
    "MsgBody": [ // Message modified by the app backend. If the app backend does not modify the message, the message sent by the user is delivered.
        {
            "MsgType": "TIMTextElem", // Text
            "MsgContent":{
                "Text": "red packet"
            }
        },
        {
            "MsgType": "TIMCustomElem", // Custom message
            "MsgContent":{
                "Desc": " CustomElement.MemberLevel ", // Description
                "Data": " LV1" // Data
            }
        }
    ],
    "CloudCustomData": "your new cloud custom data" // Custom message data
}
Response fields
Field
Type
Required
Description
ActionStatus
String
Yes
Request result. OK: Successful; FAIL: Failed
ErrorCode
Integer
Yes
Error code returned. 0: allows message sending; 1: forbids message sending; 2: discards the message silently. If the business side wants to forbid a user to send messages and send ErrorCode and ErrorInfo to the client, ensure that the value of ErrorCode is set within the range of [120001, 130000].
ErrorInfo
String
Yes
Error information
MsgBody
Array
No
Message body modified by the app backend. The Chat backend sends the modified message to the recipient. For more information on the format, see Message Formats.
CloudCustomData
String
No
Custom message data modified by the app backend. It is saved in the cloud and will be sent to the peer end. Such data can be pulled after the app is uninstalled and reinstalled. The Chat backend sends the modified message to the recipient.
References
Webhook Overview
After One-to-One Message Is Sent
Sending One-to-One Messages to One User
Sending One-to-One Messages to Multiple Users

Overview
Limits
Webhook Triggering Scenarios
Webhook Triggering Timing
API Calling Description
References

Parameter	Description
https	The request protocol is HTTPS, and the request method is POST.
[www.example.com](http://www.example.com)	Callback URL
SdkAppid	The `SDKAppID` assigned by the Chat console when the app is created
CallbackCommand	The value is always `C2C.CallbackBeforeSendMsg`.
contenttype	Always `json`
ClientIP	Client IP, such as 127.0.0.1
OptPlatform	Client platform. For valid values, see the description of `OptPlatform` in the Webhook Protocols section of Webhook Overview.

Field	Type	Description
CallbackCommand	String	Webhook command
From_Account	String	`UserID` of the message sender
To_Account	String	`UserID` of the message recipient
MsgSeq	Integer	Sequence number of the message. It is used to identify the message and the value is a random 32-bit unsigned integer.
MsgRandom	Integer	Random number of the message. It is used to identify the message and the value is a random 32-bit unsigned integer.
MsgTime	Integer	Timestamp in seconds indicating when the message is sent. One-to-one messages are preferentially sorted by `MsgTime`. Messages sent in the same second are sorted by `MsgSeq`. Messages with larger values of `MsgSeq` are after those with smaller values.
MsgKey	String	Unique identifier of the message. It can be used to recall the message via a RESTful API call.
OnlineOnlyFlag	Integer	The value is `1` if it is an online message and `0` if it's not.
MsgBody	Array	Message body. For more information, see Message Formats.
CloudCustomData	String	Custom message data. It is saved in the cloud and will be sent to the receiver. Such data can be pulled after the app is uninstalled and reinstalled.

Field	Type	Required	Description
ActionStatus	String	Yes	Request result. `OK`: Successful; `FAIL`: Failed
ErrorCode	Integer	Yes	Error code returned. `0`: allows message sending; `1`: forbids message sending; `2`: discards the message silently. If the business side wants to forbid a user to send messages and send `ErrorCode` and `ErrorInfo` to the client, ensure that the value of `ErrorCode` is set within the range of [120001, 130000].
ErrorInfo	String	Yes	Error information
MsgBody	Array	No	Message body modified by the app backend. The Chat backend sends the modified message to the recipient. For more information on the format, see Message Formats.
CloudCustomData	String	No	Custom message data modified by the app backend. It is saved in the cloud and will be sent to the peer end. Such data can be pulled after the app is uninstalled and reinstalled. The Chat backend sends the modified message to the recipient.