소식 및 공지 사항

제품 업데이트

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 정책

개인 정보 보호 정책

데이터 처리 및 보안 계약

용어집

Webhooks Overview

PDF

포커스 모드

폰트 크기

마지막 업데이트 시간: 2025-05-29 11:13:39

To facilitate control over the app's features, LiveKit offers webhook capabilities.
Feature Overview
Users can configure a webhook to a specified URL via REST API. When the executed WebhookCommand is on the configuration list, it will trigger the webhook.
Notes
Only one webhook can be set per sdkAppId.
Ensure that the webhook URL is accessible.
Webhook Protocol
Third-party webhooks are based on HTTP/HTTPS protocols. The app backend must provide a webhook URL to the live platform, and Instant Chat uses a POST request to initiate a webhook to the app backend. When initiating a webhook, Chat adds the following parameters to the URL provided by the app:
Parameter
Meaning
 SdkAppId
SDKAppId assigned by the Chat console when an app is created
 WebhookCommand
Webhook Command Word
contenttype
Optional, usually set to JSON
ClientIP
Client IP address
OptPlatform
Client Platform, corresponding to different Platform Types, possible values include: RESTAPI (sending requests using REST API), Web (sending requests using Web SDK), Android, iOS, Windows, Mac, iPad, Unknown (sending requests using an unknown type of device)
Security Considerations
Related security issues are as follows:
1. HTTP transmits data in plain text, and data confidentiality cannot be guaranteed. Therefore, HTTPS is recommended.
2. It's impossible to determine whether a webhook request really comes from Live.
For request source security, we provide the Webhook Authentication solution:
1. Configure the webhook URL and enable webhook use set webhook configuration.
2. In setting webhook authentication Token, enable authentication and configure the authentication token. Then, the signature (Sign) and signing timestamp (RequestTime) will be added to the webhook request URL. The signature algorithm is Sign=sha256(TokenRequestTime).
3. The app backend authenticates the webhook request. It uses SHA256 to calculate and verify the signature based on the local authentication token and the signing timestamp (RequestTime) in the webhook URL. The RequestTime is also checked for timeliness. If the difference between the RequestTime and the current time exceeds 1 minute, it is considered an invalid request to prevent replay attacks.
Signature algorithm sample:
﻿
Token=xxxxyyyy
RequestTime=1669872112
Sign=sha256(xxxxyyyy1669872112)=17773bc39a671d7b9aa835458704d2a6db81360a5940292b587d6d760d484061
﻿
Webhook URL=URL&Sign=17773bc39a671d7b9aa835458704d2a6db81360a5940292b587d6d760d484061&RequestTime=1669872112
Common Reasons for Webhook Failures
If a webhook failure occurs, check whether the configured webhook service has a problem according to the following checklist:
Webhook Failure Symptom
Possible Reason
Access to the webhook URL times out
1. Live cannot complete DNS resolution. In this case, check whether the domain name is valid on the public network. For example, if the webhook host is http://notexist.com, Live cannot complete DNS resolution because this domain name does not exist. 
2. Live cannot access the IP address configured in the webhook URL. In this case, check whether this IP address is accessible from the public network. For example, if the webhook host is http://10.0.0.1, Live cannot access this IP address because the domain name is a private IP address of the app.
3. The failure occurs due to the firewall policy of the app webhook service. In this case, check the firewall configuration. For example, a webhook failure occurs if the app webhook server denies all requests arriving at port 80.
Access denied by the webhook service
Live can access the host, but a connection is not established. In this case, check whether the WebServer has started properly. For example, a webhook failure will occur when the WebServer of the app webhook server has not started or when the port configuration is incorrect.
The HTTP return code of the webhook service is not 200
The webhook request is successful, but the HTTP return code in the response packet is not 200.
The webhook response packet could not be parsed
The webhook response packet is not in JSON format.
﻿

도움말 및 지원

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

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

피드백

tencent cloud

Tencent Real-Time Communication

Webhooks Overview

Feature Overview

Notes

Webhook Protocol

Security Considerations

Common Reasons for Webhook Failures

도움말 및 지원

Parameter	Meaning
SdkAppId	SDKAppId assigned by the Chat console when an app is created
WebhookCommand	Webhook Command Word
contenttype	Optional, usually set to JSON
ClientIP	Client IP address
OptPlatform	Client Platform, corresponding to different Platform Types, possible values include: RESTAPI (sending requests using REST API), Web (sending requests using Web SDK), Android, iOS, Windows, Mac, iPad, Unknown (sending requests using an unknown type of device)

Webhook Failure Symptom	Possible Reason
Access to the webhook URL times out	1. Live cannot complete DNS resolution. In this case, check whether the domain name is valid on the public network. For example, if the webhook host is http://notexist.com, Live cannot complete DNS resolution because this domain name does not exist. 2. Live cannot access the IP address configured in the webhook URL. In this case, check whether this IP address is accessible from the public network. For example, if the webhook host is http://10.0.0.1, Live cannot access this IP address because the domain name is a private IP address of the app. 3. The failure occurs due to the firewall policy of the app webhook service. In this case, check the firewall configuration. For example, a webhook failure occurs if the app webhook server denies all requests arriving at port 80.
Access denied by the webhook service	Live can access the host, but a connection is not established. In this case, check whether the WebServer has started properly. For example, a webhook failure will occur when the WebServer of the app webhook server has not started or when the port configuration is incorrect.
The HTTP return code of the webhook service is not 200	The webhook request is successful, but the HTTP return code in the response packet is not 200.
The webhook response packet could not be parsed	The webhook response packet is not in JSON format.