tencent cloud

Chat

Callback for Group Message Edit

Download
Modo Foco
Tamanho da Fonte
Última atualização: 2026-07-14 15:13:55

Overview

Use this webhook to monitor real-time group message edits performed by users in the App.

Notes

To enable the webhook, configure the webhook URL and activate the corresponding switch. For setup instructions, see the Third-Party Webhook Configuration documentation.
The webhook is triggered from the Chat backend and sent to the App backend via an HTTPS POST request.
Upon receiving a webhook request, the App backend must verify that the SDKAppID parameter in the request URL matches its own SDKAppID.
For further security considerations, refer to Third-Party Webhook Introduction: Security Considerations.

Scenarios That Trigger the Webhook

Users edit group messages in the client.
App administrators update group chat history messages by calling the REST API Modify Group Chat History Message.

Webhook Trigger Timing

The webhook is sent after a group chat message is successfully modified.

API Description

Request URL

In this example, the webhook URL configured on the App is https://www.example.com.
Example:
https://www.example.com?SdkAppid=$SDKAppID&CallbackCommand=$CallbackCommand&contenttype=json&ClientIP=$ClientIP&OptPlatform=$OptPlatform

Query Parameters

Parameter
Description
https
Request protocol is HTTPS; request method is POST.
www.example.com
Webhook URL.
SdkAppid
SDKAppID assigned in the Chat console when creating the application.
CallbackCommand
Fixed value: Group.CallbackAfterModifyMsg.
contenttype
Request body is always json.
ClientIP
Client IP address, e.g., 127.0.0.1.
OptPlatform
Client platform. See Third-Party Webhook Introduction: Webhook Protocol for details on OptPlatform parameters.

Request Example

{
"MsgBody": [
{
"MsgType": "TIMTextElem",
"MsgContent": {
"Text": "2026-03-06T02:09:35.302Z"
}
}
],
"CallbackCommand": "Group.CallbackAfterModifyMsg",
"Operator_Account": "oper-user",
"GroupId": "group-test-2",
"TopicId": "",
"MsgSeq": 53,
"EventTime": 1772762975589
}

Request Fields

Field
Type
Description
MsgBody
Array
Message content. For details on formatting, see Message Format Description. Note: A single message may contain multiple elements; MsgBody is an array.
CallbackCommand
String
Webhook command.
Operator_Account
String
UserID of the user who modified the message.
GroupId
String
ID of the group where the message was edited.
TopicId
String
Topic ID. If present, indicates the message modification applies to a historical message within the specified topic. This option is only supported for community topics.
MsgSeq
Integer
Sequence number of the message being modified.
EventTime
Integer
Timestamp (in milliseconds) when the event occurred.

Response Example

{
"ActionStatus": "OK",
"ErrorInfo": "",
"ErrorCode": 0 // 0 means webhook succeeded, 1 means webhook failed
}

Response Fields

Field
Type
Required
Description
ActionStatus
String
Required
Result of request processing:
OK: indicates success.
FAIL: indicates failure.
ErrorCode
Integer
Required
Error code:
0: webhook succeeded.
1: webhook failed.
ErrorInfo
String
Required
Error message.

References

Ajuda e Suporte

Esta página foi útil?

comentários