기능 및 서버 인터페이스
  • 클라우드 녹화
  • CDN로 전환
  • TRTC를 통한 RTMP 통합
  • 이벤트 콜백
    • 이벤트 콜백
    • CDN으로 릴레이 콜백
    • 클라우드 레코딩 콜백
    • 서명 확인 예시
  • 메시지 보내기 및 받기
  • 접근 관리
    • 개요
    • 인가 가능한 자원 및 작업
    • 사전 설정 정책
    • 사용자 정의 정책
  • 고급 권한 제어 활성화
  • OBS WHIP를 통한 TRTC 룸으로의 푸시 방법
  • 서버 API
    • 인터페이스 분류
    • 과거 기록
    • 인터페이스 요청 보내기
      • 요청 구조
      • 범용 매개변수
      • 서명 방법 v3
      • 서명
      • 회신
    • 룸 관리 인터페이스
      • SetUserBlockedByStrRoomId
      • SetUserBlocked
      • RemoveUser
      • DismissRoom
      • RemoveUserByStrRoomId
      • DismissRoomByStrRoomId
    • 통화 품질 모티터링 인터페이스
      • DescribeRoomInfo
      • DescribeUserEvent
      • DescribeCallDetailInfo
      • DescribeUserInfo
      • DescribeScaleInfo
    • 푸시 풀링 관련 인터페이스
      • StartStreamIngest
      • StopStreamIngest
      • DescribeStreamIngest
    • 클라우드 레코딩 인터페이스
      • CreateCloudRecording
      • DescribeCloudRecording
      • ModifyCloudRecording
      • DeleteCloudRecording
    • 혼합 스트림 릴레이 관련 인터페이스
      • UpdatePublishCdnStream
      • StartPublishCdnStream
      • StopPublishCdnStream
    • 사용량 통계 관련 인터페이스
      • DescribeTrtcUsage
      • DescribeRecordingUsage
      • DescribeMixTranscodingUsage
      • DescribeRelayUsage
      • DescribeTrtcRoomUsage
    • 데이터 유형
    • 에러코드
    • 부록
      • 이벤트 ID 매핑표
이 페이지는 현재 영어로만 제공되며 한국어 버전은 곧 제공될 예정입니다. 기다려 주셔서 감사드립니다.

요청 구조

1. Service Address

The API supports access from either a nearby region (at trtc.tencentcloudapi.com) or a specified region (at trtc.ap-guangzhou.tencentcloudapi.com for Guangzhou, for example).

We recommend using the domain name to access the nearest server. When you call an API, the request is automatically resolved to a server in the region nearest to the location where the API is initiated. For example, when you initiate an API request in Guangzhou, this domain name is automatically resolved to a Guangzhou server, the result is the same as that of specifying the region in the domain like "trtc.ap-guangzhou.tencentcloudapi.com".

Note: For latency-sensitive businesses, we recommend that you specify the region in the domain name.

Tencent Cloud currently supports the following regions:

Hosted regionDomain name
Local access region (recommended, only for non-financial availability zones)trtc.tencentcloudapi.com
South China (Guangzhou)trtc.ap-guangzhou.tencentcloudapi.com
East China (Shanghai)trtc.ap-shanghai.tencentcloudapi.com
North China (Beijing)trtc.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu)trtc.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing)trtc.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China)trtc.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore)trtc.ap-singapore.tencentcloudapi.com
Southeast Asia (Bangkok)trtc.ap-bangkok.tencentcloudapi.com
South Asia (Mumbai)trtc.ap-mumbai.tencentcloudapi.com
Northeast Asia (Seoul)trtc.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo)trtc.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia)trtc.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley)trtc.na-siliconvalley.tencentcloudapi.com
North America (Toronto)trtc.na-toronto.tencentcloudapi.com
Europe (Frankfurt)trtc.eu-frankfurt.tencentcloudapi.com

2. Communications Protocol

All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communication tunnels.

3. Request Methods

Supported HTTP request methods:

  • POST (recommended)
  • GET

The Content-Type types supported by POST requests:

  • application/json (recommended). The TC3-HMAC-SHA256 signature algorithm must be used.
  • application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature algorithm must be used.
  • multipart/form-data (only supported by certain APIs). You must use TC3-HMAC-SHA256 to calculate the signature.

The size of a GET request packet is up to 32 KB. The size of a POST request is up to 1 MB when the HmacSHA1 or HmacSHA256 signature algorithm is used, and up to 10 MB when TC3-HMAC-SHA256 is used.

4. Character Encoding

Only UTF-8 encoding is used.