Skip to main content

Callback After User Quits Group

Functional Description

After a successful operation, the business server can perform necessary data synchronization or other business logic processing through this callback.

Precautions

  • To enable the callback, you must configure the callback URL and turn on the switch corresponding to this callback protocol. See the Callback Description document for configuration methods.
  • The callback direction is an HTTP/HTTPS POST request initiated by IMServer to the business server.
  • The business server must respond to this request within the timeout period.

Scenarios That May Trigger This Callback

  • After users perform corresponding operations successfully through the client or APP administrators through REST API.

Timing of Callback

  • After a user successfully quits a group.

Interface Description

Request URL Example

Here CallbackCommand is: callbackAfterQuitGroupCommand

{WEBHOOK_ADDRESS}/callbackAfterQuitGroupCommand?contenttype=json

Request Package Example

{
"callbackCommand": "callbackAfterQuitGroupCommand",
"groupID": "G001",
"userID": "user123"
}

Request Package Field Description

FieldTypeDescription
callbackCommandstringCallback command, here it is the callback after a user quits the group
groupIDstringUnique identifier of the group the user attempted to quit
userIDstringUser ID attempting to quit the group

Response Package Example

{
"actionCode": 0,
"errCode": 0,
"errMsg": "",
"errDlt": "",
"nextCode": 0
}

Response Package Field Description

FieldValueDescription
actionCode0Indicates whether the business system callback was executed correctly. 0 means the operation was successful.
errCode0Custom error code, 0 here means ignore the callback result.
errMsg"An error message"Simple error message corresponding to the custom error code.
errDlt"Detailed error information"Detailed error information corresponding to the custom error code.
nextCode1Next execution instruction, 1 means refusing to continue execution, set when actionCode is 0.