tencent cloud

Tencent Real-Time Communication

소식 및 공지 사항
제품 업데이트
Tencent Cloud 오디오/비디오 단말 SDK 재생 업그레이드 및 권한 부여 인증 추가
TRTC 월간 구독 패키지 출시 관련 안내
제품 소개
제품 개요
기본 개념
제품 기능
제품 장점
응용 시나리오
성능 데이터
구매 가이드
Billing Overview
무료 시간 안내
Monthly subscription
Pay-as-you-go
TRTC Overdue and Suspension Policy
과금 FAQ
Refund Instructions
신규 사용자 가이드
Demo 체험
Call
개요(TUICallKit)
Activate the Service
Run Demo
빠른 통합(TUICallKit)
오프라인 푸시
Conversational Chat
온클라우드 녹화(TUICallKit)
AI Noise Reduction
UI 사용자 정의
Calls integration to Chat
Additional Features
No UI Integration
Server APIs
Client APIs
Solution
ErrorCode
릴리스 노트
FAQs
라이브 스트리밍
Billing of Video Live Component
Overview
Activating the Service (TUILiveKit)
Demo 실행
No UI Integration
UI Customization
Live Broadcast Monitoring
Video Live Streaming
Voice Chat Room
Advanced Features
Client APIs
Server APIs
Error Codes
Release Notes
FAQs
RTC Engine
Activate Service
SDK 다운로드
API 코드 예시
Usage Guidelines
API 클라이언트 API
고급 기능
RTC RESTFUL API
History
Introduction
API Category
Room Management APIs
Stream mixing and relay APIs
On-cloud recording APIs
Data Monitoring APIs
Pull stream Relay Related interface
Web Record APIs
AI Service APIs
Cloud Slicing APIs
Cloud Moderation APIs
Making API Requests
Call Quality Monitoring APIs
Usage Statistics APIs
Data Types
Appendix
Error Codes
콘솔 가이드
애플리케이션 관리
사용량 통계
모니터링 대시보드
개발 보조
Solution
Real-Time Chorus
FAQs
과금 개요
기능 관련
UserSig 관련
방화벽 제한 처리
설치 패키지 용량 축소 관련 질문
Andriod 및 iOS 관련
Web 관련
Flutter 관련
Electron 관련
TRTCCalling Web 관련
멀티미디어 품질 관련
기타 질문
Protocols and Policies
컴플라이언스 인증
보안 백서
정보 보안에 관한 참고 사항
Service Level Agreement
Apple Privacy Policy: PrivacyInfo.xcprivacy
TRTC 정책
개인 정보 보호 정책
데이터 처리 및 보안 계약
용어집
문서Tencent Real-Time Communication라이브 스트리밍Server APIsThird-Party WebhooksBattle RelatedWebhook After Creating Battle

Webhook After Creating Battle

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-27 11:42:01

Feature Description

The app server can use this webhook to monitor battle started.

Must-Knows

To enable the webhook, the webhook must be configured URL, and turn on the switch corresponding to this webhook protocol. For configuration methods, see Third-party Webhook Configuration Document.
The direction of the webhook is that the live backend initiates an HTTP POST request to the app backend.
After receiving the webhook request, the app backend must verify whether the parameter SDKAppID in the request URL is its own SDKAppID.

Scenarios That May Trigger This Webhook

After creating a battle with , it can directly enter the started state without waiting when .
After the battle is created, once all callees have processed the battle request, as long as there is at least one room owner of the callee who agrees to join the battle, the battle officially begins.

Timing Of Webhook Occurrence

After the battle is officially launched.

API Description

Request URL Sample:

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

Description Of Request Parameters

Parameter
Description
https
Request Protocol: HTTPS, Request Method: POST.
www.example.com
Webhook URL.
SdkAppid
The SDKAppID assigned in the Chat console when creating an application.
CallbackCommand
Fixed as Live.CallbackAfterStartBattle.
contenttype
The fixed value is json.
ClientIP
Client IP, format as: 127.0.0.1.
OptPlatform
Client platform. For the value, see Introduction to Third-Party Webhook for the parameter meaning of OptPlatform.

Request Packet Sample

{
    "CallbackCommand": "Live.CallbackAfterStartBattle",  
    "BattleId": "4siHsNsWN/T3aub9zKraqI4zZAyPRpXQhdtKv1q4HOs=", // battle id
    "Duration": 60000, // battle duration
    "CreateTime": 1739954005, // battle creation time, in seconds
    "StartTime": 1739954005, // battle start time, in seconds
    "FromRoomInfo": {  // Caller information in battle
        "RoomId": "pk-3",
        "Owner_Account": "brennan"
    },
    "ToRoomList": [ // Called party information in battle
        {
            "RoomId": "pk-5",
            "Owner_Account": "tandy"
        }
    ],
    "EventTime": 1739954005000, // Callback trigger time, in milliseconds
}

Description Of Request Packet Fields

Field
Type
Description
CallbackCommand
String
Webhook command.
BattleId
String
Battle ID.
Duration
Integer
Battle duration in milliseconds.
CreateTime
Integer
Creation time of the battle, Unix time.
StartTime
Integer
Start time of the battle, Unix time.
FromRoomInfo
String
Caller information in battle.
ToRoomList
Array
Information of the callee participating in the battle.
RoomId
String
Room ID.
Owner_Account
String
The owner ID of room.
EventTime
Integer
Millisecond-level timestamp triggered by the event.

Response Packet Example

After the app synchronizes data in the background, it sends a webhook response packet.
{
    "ActionStatus": "OK",
    "ErrorInfo": "",
    "ErrorCode": 0 // Ignore webhook result
}

Description Of Response Packet Fields

Field
Type
Attribute
Description
ActionStatus
String
Required
Result of request processing. OK indicates success and FAIL indicates failure.
ErrorCode
Integer
Required
Error code. Fill in 0 here to ignore the webhook result.
ErrorInfo
String
Required
Error message.

Reference

Introduction to Third-Party Webhook
이전 주제: Webhook After Creating Battle다음 주제: Webhook After Ending Battle

도움말 및 지원

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

피드백