제품 소개

제품 개요

Basic Concepts

응용 시나리오

기능 소개

계정 시스템

사용자 정보 및 관계망

메시지 관리

그룹 시스템

Official Account

Audio/Video Call

사용 제한

구매 가이드

과금 개요

요금 안내

Purchase Instructions

Renewal Guide

연체 안내

Refund Policy

다운로드 센터

SDK & Demo 소스 코드

업데이트 로그

시나리오 솔루션

Live Streaming Setup Guide

AI Chatbot

대규모 엔터테인먼트 협업 커뮤니티

Discord 구현 가이드

IM을 게임에 통합하는 방법

WhatsApp Channel-style Official Account Integration Solution

Send Red Packet

Firewall Restrictions

클라이언트 APIs

SDK API(Web)

Android

iOS & macOS

Swift

Flutter

Electron

Unity

React Native

C APIs

C++

서버 APIs

Secure authentication with UserSig

RESTful APIs

Webhooks

콘솔 가이드

New Console Introduction

애플리케이션 생성 및 업그레이드

기본 설정

기능 설정

계정 관리

그룹 관리

Official Channel Management

콜백 설정

모니터링 대시보드

Viewing Guide for Resource Packages

Real-Time Monitor

개발 보조 툴

액세스 관리

Advanced Features

FAQ

uni-app FAQs

구매

SDK 관련 질문

계정 인증

사용자 정보 및 관계망

메시지

그룹

라이브 방송 그룹

닉네임 및 프로필 사진

협약 및 인증

Service Level Agreement

컴플라이언스 인증

IM 정책

개인 정보 보호 정책

데이터 개인 정보 보호 및 보안 계약

에러 코드

문의하기

Webhook for Online and Offline Status of Audio-Video Group Members

PDF

포커스 모드

폰트 크기

마지막 업데이트 시간: 2025-10-28 10:25:17

Feature Overview
This webhook allows you to view the online and offline status (such as record logs) of an audio-video group in real time or synchronize the information to other systems on the app backend. 
Reminders
To use this webhook, you need to purchase the Pro edition 、Pro Plus edition or Enterprise edition and enable the List of online audio-video group members feature on the Group feature configuration page in the console. After the feature is enabled in the console, the list of the latest 1,000 online members of an audio-video group will be stored and the list can be pulled on clients. If the feature is disabled in the console, the list cannot be pulled on clients, and only the list of the 30 latest group members can be pulled.
To enable this webhook, you must configure a webhook URL and toggle on the corresponding protocol. For more information on the configuration method, see Webhook Configuration.
During this webhook event, the Chat backend initiates an HTTP 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.
For more security considerations, see the Security Considerations section inWebhook Overview.﻿
Webhook Triggering Scenarios
App users abnormally exit after entering the audio-video group. The system performs an internal check every 20 seconds. If it detects that a user has not reported a heartbeat for over 30 seconds, it triggers an offline callback. 
App users abnormally exit after entering the audio-video group. After an offline callback is triggered by the absence of a heartbeat, a subsequent online callback will be initiated upon heartbeat reported.
App users first join the audio-video group. When a user joins the same audio-video group from multiple App terminals, where the App terminals include the Web terminal, the online callback is triggered only once.
App user's last active exit from the audio-video group. When a user has multiple App terminals in the audio-video group, where the App terminals include the Web terminal, the offline callback is triggered when the last terminal exits.
Webhook Triggering Timing
After a user enters the audio-video group, the Offline event is triggered due to heartbeat timeout caused by network disconnection, and the Online event is triggered when the user goes online 20s after the timeout. If the user logs in with multiple devices and joins the same audio-video group concurrently, the Offline event will be triggered when all the devices go offline concurrently. The Online event will be triggered when any device goes back online (only one Online event will be triggered even if multiple devices go back online).
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
Request parameters
Parameter
Description
https
The request protocol is HTTPS, and the request method is POST.
www.example.com
Callback URL
SdkAppid
The SDKAppID assigned by the Chat console when the app is created
CallbackCommand
Fixed value: Group.CallbackOnMemberStateChange.
contenttype
Fixed value: JSON.
Sample request
{
    "CallbackCommand": "Group.CallbackOnMemberStateChange", // Webhook command
    "GroupId": "@TGS#2J4SZEAEL", // Group ID
    "EventType": "Offline", // Event type: Offline (disconnected); Online (reconnected)
    //Event Cause: HeartbeatInterrupt (Heartbeat Interruption), HeartbeatRecover (Heartbeat Recovery), Join (First Entry into Group), Quit (Last Exit from Group)
    "MemberList": [ // List of members who left the group
        {
            "Member_Account": "jared"
        },
        {
            "Member_Account": "tommy"
        }
    ],
    "EventTime":"1670574414123"// Event trigger timestamp in milliseconds	
}
Request fields
Field
Type
Description
CallbackCommand
String
Webhook command
GroupId
String
ID of the group that generates group messages
EventType
String
Event type: Offline (disconnected); Online (reconnected)
EventCause
String
Event cause: HeartbeatInterrupt (heartbeat interruption), HeartbeatRecover (heartbeat recovery), Join (first entry into group), Quit (last exit from group)
MemberList
Array
List of members triggering the event
Sample response
A response is returned after the app backend synchronizes the data.
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 0 // The value `0` indicates that the response result is ignored.
}
Response fields
Field
Type
Required
Description
ActionStatus
String
Yes
Request result. OK: Successful; FAIL: Failed
ErrorCode
Integer
Yes
Error code. The value 0 indicates that the response result is ignored.
ErrorInfo
String
Yes
Error information
References
Webhook Overview
After a User Joins a Group
After a User Leaves a Group

도움말 및 지원

문제 해결에 도움이 되었나요?

더 자세한 내용은 문의하기 또는 티겟 제출 을 통해 문의할 수 있습니다.

피드백

Parameter	Description
https	The request protocol is HTTPS, and the request method is POST.
www.example.com	Callback URL
SdkAppid	The `SDKAppID` assigned by the Chat console when the app is created
CallbackCommand	Fixed value: `Group.CallbackOnMemberStateChange`.
contenttype	Fixed value: `JSON`.

Field	Type	Description
CallbackCommand	String	Webhook command
GroupId	String	ID of the group that generates group messages
EventType	String	Event type: Offline (disconnected); Online (reconnected)
EventCause	String	Event cause: HeartbeatInterrupt (heartbeat interruption), HeartbeatRecover (heartbeat recovery), Join (first entry into group), Quit (last exit from group)
MemberList	Array	List of members triggering the event

Field	Type	Required	Description
ActionStatus	String	Yes	Request result. `OK`: Successful; `FAIL`: Failed
ErrorCode	Integer	Yes	Error code. The value `0` indicates that the response result is ignored.
ErrorInfo	String	Yes	Error information

tencent cloud

Chat

Webhook for Online and Offline Status of Audio-Video Group Members

Feature Overview

Reminders

Webhook Triggering Scenarios

Webhook Triggering Timing

API Calling Description

Sample request URL

Request parameters

Sample request

Request fields

Sample response

Response fields

References

도움말 및 지원