# Live > Interactive live streaming SDK for co-hosting, audience interaction, virtual gifts, live chat, beauty effects, AI noise suppression, ecommerce live streaming, entertainment live streaming, and voice chat room scenarios. This index is the entry point for LLMs. It links to shared product-level docs and to one `llms.txt` per supported platform. Each linked page also has a `.md` twin (append `.md` to the URL) containing the raw markdown. ## Platforms https://pre.trtc.io/llms/live/ios.txt https://pre.trtc.io/llms/live/android.txt https://pre.trtc.io/llms/live/vue.txt https://pre.trtc.io/llms/live/electron.txt https://pre.trtc.io/llms/live/react-native.txt https://pre.trtc.io/llms/live/flutter.txt https://pre.trtc.io/llms/live/react.txt https://pre.trtc.io/llms/live/web.txt ## Basics - [Introduction](https://pre.trtc.io/document/60034.md): Overview Live is a real-time interactive live streaming SDK designed for Android, iOS, Desktop, Flutter, and Web platforms. It enables developers to quickly integrate live streaming capabilities including anchor broadcast, audience interaction via chat and emojis, likes, gift-giving, and multi-guest management. The SDK supports high-definition streaming, voice chat rooms, audience management, and advanced features like gift systems, network optimization, and beauty AR effects, making it ideal for entertainment, e-commerce, education, and other large-scale live streaming scenarios. - [Activate Service](https://pre.trtc.io/document/60033.md): Tencent RTC Live SDK offers a 14-day trial and official monthly subscription packages to enable audio and video live streaming. This guide helps developers activate trial services, purchase official editions, renew or upgrade subscriptions, and enable automatic renewal through the Tencent RTC console. It supports deployment in Singapore and Silicon Valley, providing step-by-step instructions to manage your TRTC Live applications efficiently. - [Product Introduction](https://pre.trtc.io/document/74811.md): AtomicXCore SDK is a UI-less integration platform designed for real-time interactive applications including Video Live Streaming, Conferencing, Voice Chat Rooms, and Calling. It targets developers building custom user interfaces by encapsulating complex business logic such as HD streaming, audience co-hosting, cross-room connections, live chat, and interactive gifting. The SDK supports Android, iOS, and Web platforms with comprehensive quick start guides. AtomicXCore leverages a Store-based state management system to handle business logic and asynchronous events efficiently, enabling rapid development of highly customizable interactive experiences. ## Billing - [Free Quota](https://pre.trtc.io/document/42735.md): Tencent RTC Free Minutes is a monthly usage benefit for Tencent Cloud accounts with an active TRTC package, providing 10,000 free minutes for various audio and video services including calls, conferences, live streaming, and AI-powered features. This overview explains eligibility, usage deduction ratios by service type and resolution, expiration policies, and billing transitions when free minutes are exhausted. It helps users understand how free minutes apply to their TRTC usage and manage their package effectively. - [Live Monthly Packages](https://pre.trtc.io/document/59407.md): TRTC Live (TUILiveKit) is a real-time interactive live streaming SDK that enables developers to integrate interactive live video streaming and voice room features into their apps on Android, iOS, Flutter, and Electron platforms. This overview explains the pricing structure including monthly package fees, pay-as-you-go charges, and MAU billing methods. It also details package validity, billing at the application level, and recommendations for managing subscriptions to ensure uninterrupted service. - [Usage-based Billing](https://pre.trtc.io/document/59806.md): Tencent Real-Time Communication (TRTC) subscription package duration billing overview explains how free monthly minutes are used to deduct TRTC audio and video usage. This prepaid package system applies to specific SDKAppIDs and is valid for one month from purchase. It details deduction order, expiration policies, pay-as-you-go charges for excess usage, and refund conditions. The document also clarifies deduction ratios based on media type and video resolution, helping users understand billing calculations and manage their package usage effectively. - [Audio/Video Duration Billing](https://pre.trtc.io/document/42734.md): Tencent Real-Time Communication (TRTC) billing documentation explains the audio and video duration billing model for RTC Engine, Call, Conference, and Live Audio Room components. It details daily pay-as-you-go billing, prepaid package usage, pricing by video resolution categories, and free usage quotas. This guide helps developers understand cost calculation, billing cycles, and additional fees for stream relaying and other TRTC services. - [Video Live Component Billing](https://pre.trtc.io/document/66078.md): The Video Live component by Tencent RTC is a live streaming SDK designed for large-scale single-room scenarios with millions of concurrent viewers. It offers duration-based billing that covers anchor and audience streaming times, as well as transcoding fees for multi-anchor setups. This overview explains the billing formulas, pricing tiers by resolution and codec, and usage statistics to help users understand cost calculation and manage their live streaming expenses effectively. ## Build with AI - [Overview](https://pre.trtc.io/document/77713.md): Tencent RTC Overview provides a comprehensive guide to integrating AI tools with Chat, Live, Call, Conference, and RTC Engine. It introduces the Model Context Protocol (MCP) server for automated credential generation and supported tools, Agent Skills for natural language task workflows, and LLMs.txt Markdown indexes for documentation. This overview helps developers quickly start, implement scenarios, and access official knowledge base resources with ease. - [Configure MCP Server](https://pre.trtc.io/document/78382.md): The MCP Server configuration guide provides step-by-step instructions to set up the AI-powered MCP solution for TRTC Knowledge Query and UI-Integrated Feature Implementation. This guide helps developers configure MCP in various AI development environments such as Cursor, Codex, Claude, and others by setting necessary environment variables and verifying the setup. It supports multiple platforms including Web, Android, iOS, and Flutter, enabling efficient integration of real-time audio/video features and API queries. - [Install Skills](https://pre.trtc.io/document/78383.md): TRTC Agent Skills is an AI-powered integration assistant SDK designed to simplify the integration of Tencent RTC products. It supports multiple IDEs and guides developers through installation, configuration, and feature integration with natural language commands. This guide covers installation steps, session reload instructions, and how to get started using the Skill for running demos, adding features, troubleshooting, and querying documentation. ## Get Started - [Video Live Streaming](https://pre.trtc.io/document/74594.md): The AtomicXCore SDK offers a lightweight core component LiveCoreView for iOS developers to build live streaming applications with host broadcasting and audience viewing capabilities. This quick start guide walks you through activating the service, importing the SDK into your project, configuring necessary permissions, implementing login logic, and creating a basic live streaming room. Follow these steps to enable live stream publishing, playback, and event handling in your app. - [Voice Chat Room](https://pre.trtc.io/document/74682.md): The AtomicXCore SDK for iOS provides a voice chat room SDK enabling host broadcasting and audience participation. This quickstart guide walks you through activating the service, importing the SDK, implementing login logic, and building a basic voice chat room with live streaming and seat management. It covers key steps such as creating a host room, audience joining, and testing, along with advanced features like speaking wave animation and custom status synchronization. ## Video Interaction - [Guest Connection](https://pre.trtc.io/document/74598.md): AtomicXCore CoGuestStore is an SDK module designed for iOS to manage audience co-hosting workflows in live streaming. It simplifies signaling and state synchronization by providing intuitive methods for audience members to request co-hosting and for hosts to invite viewers. This guide covers integration steps, handling requests and responses, and managing co-host lifecycle events to enable seamless audio and video interaction between viewers and hosts. - [Live Battles](https://pre.trtc.io/document/74600.md): AtomicXCore SDK for iOS enables live battle scenarios by integrating CoHostStore for cross-room co-hosting and BattleStore for PK battles. This quickstart guide walks developers through the step-by-step process of setting up component integration, implementing co-hosting between two hosts, initiating PK challenges, and managing real-time PK battles within a live streaming environment. - [Beauty Effects](https://pre.trtc.io/document/74606.md): AtomicXCore BaseBeautyStore is an iOS SDK module for managing basic portrait beautification effects in live streaming and video calling applications. This quickstart guide walks you through integrating the component, obtaining the singleton instance, subscribing to real-time beautification state updates, setting smoothing, whitening, and rosy cheek intensities, and resetting beautification effects. Follow these steps to easily add natural beautification features to your app. ## Voice Interaction - [Guest Connection](https://pre.trtc.io/document/74684.md): AtomicXCore offers CoGuestStore and LiveSeatStore SDK modules for iOS to enable voice mic-link functionality in live streaming apps. This quickstart guide helps developers implement key features such as audience mic-link requests, host invitations, and mic seat management with simple method calls, streamlining real-time audio interaction between hosts and viewers. - [Live Battles](https://pre.trtc.io/document/74690.md): AtomicXCore SDK provides CoHostStore and BattleStore modules to enable cross-room co-hosting and PK battles in iOS voice chat applications. This quickstart guide walks developers through integrating these modules with step-by-step instructions including fetching active streamers, sending co-hosting invitations, handling invitation responses, rendering co-hosting UI layouts, inviting additional streamers, exiting co-hosting sessions, and managing PK battles with score updates and winner determination. ## Common Interactive Features - [Live Stream List](https://pre.trtc.io/document/74610.md): AtomicXCore Live Streaming SDK for iOS enables developers to manage live room lists, create and join live rooms, and maintain room states. This quickstart guide walks through integrating core components, fetching live room lists, and implementing audience entry from the live room list using UICollectionView. It supports both video live streaming and voice chat room scenarios, providing a comprehensive live streaming lifecycle management solution. - [Audience Management](https://pre.trtc.io/document/74596.md): LiveAudienceStore in AtomicXCore is an SDK module for iOS that enables real-time audience list and management in live streaming rooms. This guide walks through integrating the component, initializing the audience list, subscribing to state and events, and managing audience roles and presence. It helps developers implement live viewer tracking, event handling, and administrative controls for live streaming applications on iOS. - [Virtual Gifts](https://pre.trtc.io/document/74604.md): GiftStore within AtomicXCore is an iOS SDK module designed to manage live room gifting features for live streaming apps. It enables developers to implement a full gifting system supporting gift list retrieval, sending virtual gifts, and real-time event synchronization. This guide covers key integration steps including component setup, initializing the GiftStore instance, subscribing to gift events and gift list updates, and sending gifts to enhance interactive live streaming experiences. - [Live Comments](https://pre.trtc.io/document/74602.md): This guide provides iOS developers with a detailed quickstart for integrating the BarrageStore live chat overlay SDK into live streaming apps. It covers initializing the barrage system, subscribing to real-time message updates, sending text and custom barrage messages, inserting local tip messages, and managing user speaking permissions. The document also addresses performance optimization in high-concurrency scenarios and rendering complex barrage styles, enabling developers to enhance viewer interaction effectively. - [Sound Effects](https://pre.trtc.io/document/74608.md): This guide explains how to integrate audio effect controls into iOS live streaming and voice chat applications using the AudioEffectStore and DeviceStore modules from the AtomicXCore framework. It targets developers who want to implement microphone volume adjustment, real-time ear monitoring, voice changing effects, and reverb effects. The steps include component integration, accessing singleton store instances, and managing audio effect features with example code snippets. ## Client APIs - [Overview](https://pre.trtc.io/document/66838.md): AtomicXCore SDK is a reactive API platform designed for video live streaming and voice chat rooms, enabling developers to quickly build customized UI pages. It offers comprehensive modules for user login, device management including audio effects and beauty filters, live interaction features such as PK sessions and co-hosting, as well as support for barrage and gift message handling. The SDK also includes view components for live streaming push and playback, facilitating multi-person co-guest and PK functionalities on Swift platforms. - [Define](https://pre.trtc.io/document/66857.md): This module defines common base types used across platforms, including unified error handling structures and callback closure types for API calls. It offers essential data structures such as CompletionClosure, ErrorInfo, and reactive state management tools like StatePublisher and StatePropertySelector. These components facilitate consistent asynchronous operation handling and paginated list result callbacks in Tencent RTC APIs. - [AudioEffectStore](https://pre.trtc.io/document/78051.md): AudioEffectStore is an API class in Tencent RTC that offers comprehensive audio effect management capabilities such as voice changer effects, reverb effects, and ear monitor functionality. It is intended for anchors who want to enhance live streaming by adjusting voice effects in real-time. The API provides methods to set voice changer types, reverb types, enable or disable ear monitoring, adjust ear monitor volume, and reset effects. Effects are session-based and require reapplication after leaving a room. The ear monitor feature supports wired earphones only due to Bluetooth latency limitations. - [BarrageStore](https://pre.trtc.io/document/78052.md): BarrageStore is an API suite for managing barrages in live rooms, enabling developers to send text and custom barrage messages and add local tip messages visible only to the client. It supports real-time barrage state updates via a state publisher and requires a live room ID to instantiate. This API is designed for live room and voice chat applications to implement interactive barrage features. - [BaseBeautyStore](https://pre.trtc.io/document/78053.md): BaseBeautyStore is a beauty adjustment SDK that enables real-time control of smoothness, whiteness, and ruddy levels through easy-to-use APIs. It supports subscribing to beauty state updates to synchronize UI with actual effect changes. Key APIs include methods to set individual beauty effect levels within a 0 to 9 range and reset all effects to default. This API reference details the available functions and data structures for developers integrating beauty effects in their applications. - [BattleStore](https://pre.trtc.io/document/78054.md): BattleStore API is a comprehensive SDK for managing the real-time PK (player kill) lifecycle in interactive battles between hosts. It is designed for developers building live interactive applications on Tencent RTC, providing APIs to create instances, handle PK requests, manage state updates, and respond to events with built-in timeout handling. The API supports real-time tracking of PK information, participating users, and scores through a state publisher and event-driven callbacks. - [CoGuestStore](https://pre.trtc.io/document/78055.md): CoGuestStore API is a comprehensive SDK for managing co-guest interactions in live rooms, enabling real-time seat-based communication between hosts and audience members. It provides bidirectional invitation handling, state tracking of connected users, and event-driven updates for both host and guest roles. This API supports timeout mechanisms and requires creating instances with a live room ID to manage co-guest lifecycle effectively. - [CoHostStore](https://pre.trtc.io/document/78056.md): CoHostStore API provides comprehensive interfaces to manage cross-room connections between hosts in different live rooms. It enables real-time interaction, state tracking, event monitoring, and supports multiple layout templates. Developers can create instances using a live room ID and perform connection operations such as requesting, accepting, rejecting, canceling, and exiting connections. The API also offers event publishers for observing connection state changes and recommended host lists. - [DeviceStore](https://pre.trtc.io/document/78057.md): DeviceStore SDK offers a comprehensive API suite for managing audio and video devices such as microphones, cameras, and screen sharing on supported platforms. It enables developers to control device states, adjust volumes, switch audio routes, and monitor network quality in real time. The API uses a shared singleton instance and provides detailed device status updates through subscribable data structures. - [GiftStore](https://pre.trtc.io/document/78058.md): GiftStore is a comprehensive gift management API for live rooms, enabling developers to send gifts, refresh gift lists, set display languages, and listen to gift events. It supports creating instances tied to live room IDs and delivers real-time gift state updates. This API reference details methods like create, sendGift, refreshUsableGifts, and setLanguage, along with data structures including Gift and GiftCategory to facilitate interactive gift features in live streaming applications. - [LikeStore](https://pre.trtc.io/document/78059.md): LikeStore is an API class in Tencent RTC that offers comprehensive like management capabilities for live rooms and voice chat rooms. It enables developers to send likes, listen to like events, and retrieve the current like state with real-time updates. The API requires a valid live room ID for instantiation and supports event callbacks to handle new like messages and accumulated like counts. - [LiveAudienceStore](https://pre.trtc.io/document/78060.md): LiveAudienceStore is an audience management API class for live rooms, enabling developers to manage audience lists, assign administrator roles, kick users, mute/unmute users, and listen to audience events. It provides real-time audience state updates via a state publisher and supports user roles including owner, administrator, and general user. This API reference details methods such as creating instances, fetching audience lists, setting and revoking administrators, kicking users out, and controlling message permissions. - [LiveCoreView](https://pre.trtc.io/document/66837.md): LiveCoreView is a live streaming view container component that supports video rendering, multi-person co-guest, and anchor PK features. Designed for live streaming applications, it enables interactive video playback and push within live rooms. Key capabilities include managing view layers and creating specialized views for co-guests, co-hosts, and PK sessions, requiring the live room ID to be set beforehand. - [LiveListStore](https://pre.trtc.io/document/78061.md): LiveListStore is a live room management API that enables hosts and audiences to manage the lifecycle of live rooms, including starting, joining, leaving, and ending live sessions. It provides real-time live state updates via a state publisher and supports operations such as fetching live lists, updating live info, and handling live events. This API is designed for developers integrating live broadcasting features with Tencent RTC. - [LiveSeatStore](https://pre.trtc.io/document/66860.md): LiveSeatStore is a seat management API SDK designed for live room applications, enabling developers to implement seat operations such as taking, leaving, locking, unlocking seats, and managing users by kicking or moving them. It also provides remote device control capabilities for users' cameras and microphones. The API supports real-time seat state updates via event publishers and requires creating instances with a valid live room ID. This reference details the available methods, parameters, and event handling for comprehensive seat management. - [LoginStore](https://pre.trtc.io/document/78062.md): LoginStore is a login management API class that provides user login, logout, and personal information management capabilities. It is designed for developers integrating user authentication and profile management in their applications. The API supports login using SDK application ID, user ID, and user signature, logout operations, and setting user profile information such as nickname, avatar, and gender. Real-time login status updates are available through a state publisher, and the singleton pattern ensures a consistent instance across the application. This reference covers all LoginStore APIs including login, logout, setSelfInfo, and event observation. ## All_Platform - [Account Management](https://pre.trtc.io/document/69881.md): The Chat Account Management guide provides step-by-step instructions for creating, deleting, editing, and exporting user accounts within the Chat console. It is designed for administrators managing standard and admin user accounts, detailing how to configure account types, usernames, profile information, and permissions. Key actions include enabling account deletion, batch operations, and exporting account data to support effective user management. - [Login Authentication](https://pre.trtc.io/document/69882.md): Login Authentication for Chat SDK is a core system shared by Live and Instant Messaging services, evolved from the QQ instant messaging platform. It enables apps to securely log in users using UserID and UserSig credentials, where UserSig is a password generated by the App Server with encryption. This system ensures secure access and supports app admins with elevated permissions for managing groups and users. The overview explains the login process, security considerations, and admin roles for effective Chat SDK integration. - [Generate UserSig](https://pre.trtc.io/document/69883.md): This guide explains how to generate UserSig, the encrypted signature used for user login and REST API authentication in Tencent Cloud Chat SDK. It covers generating UserSig via the console, client-side sample code, and secure server-side methods. The document provides source code for multiple programming languages and platforms and highlights best practices to protect the SECRETKEY by generating UserSig on the server. - [Profile Management](https://pre.trtc.io/document/69884.md): Chat Profile Management is a comprehensive SDK solution that enables apps to store, read, and write user profile information through standard and custom profile fields. It supports key-value formatted data with defined types and naming rules, ensuring data reliability via remote disaster recovery, cross-region deployment, and auto scaling. This service is designed for developers building live and instant messaging applications who need stable and scalable user profile hosting capabilities. - [RESTful API Overview](https://pre.trtc.io/document/63398.md): The Live Streaming Room SDK RESTful API is an HTTPS backend management interface designed for developers to manage live streaming rooms efficiently. It supports secure POST requests with JSON-formatted bodies and responses, requiring authentication parameters like sdkappid, identifier, and usersig. This overview explains the API structure, request and response formats, common error codes, and usage prerequisites to help developers integrate and troubleshoot the API effectively. - [RESTful API List](https://pre.trtc.io/document/63399.md): This RESTful API reference documents the live engine HTTP service APIs for Tencent RTC, covering room management, user management, account import, seat control, PK interactions, robot operations, and message management. It is designed for developers integrating real-time communication features, providing detailed endpoints for creating and managing rooms, handling user roles and bans, controlling seats, managing PK sessions, operating robots, and sending messages. - [Create Room](https://pre.trtc.io/document/63401.md): The CreateRoom API is a Tencent RTC server-side interface for creating live streaming or voice chat rooms. It allows developers to configure room interaction modes, UI layouts, and audio/video mixing strategies tailored for scenarios like showroom live, guest live, voice salons, and seminars. The API accepts JSON-formatted requests with detailed room parameters and supports up to 200 requests per second, enabling flexible and scalable live room management. - [Update Room Information](https://pre.trtc.io/document/63403.md): The Update Room Information API allows App Administrators to modify various attributes of chat rooms, including room name, maximum member count, mute settings, cover image, and visibility. This API supports JSON requests and requires authentication via SDKAppID and user signature. It is designed to help administrators manage room configurations efficiently with a maximum call frequency of 200 queries per second. The response includes detailed status and error information to assist in troubleshooting. - [Get Room Information](https://pre.trtc.io/document/63404.md): The Get Room Information API enables App Administrators to retrieve detailed information about chat rooms on the Tencent RTC Chat platform. This API accepts JSON requests with parameters including sdkappid, identifier, usersig, and room ID, and returns comprehensive room details such as room name, type, owner, seat settings, capacity, and activity status. It supports up to 200 queries per second and provides error codes within the response payload for troubleshooting. - [Get Room List](https://pre.trtc.io/document/63405.md): The Get Room List API is part of the Chat platform SDK that enables App Administrators to fetch a paginated list of live stream rooms sorted by view count. This API requires authentication parameters including sdkappid, identifier, and usersig, and supports JSON request and response formats. It is designed for administrators to monitor and manage live streaming rooms efficiently with a maximum call rate of 10 requests per second. - [Destroy Room](https://pre.trtc.io/document/63406.md): The Destroy Room API is part of the Tencent RTC live room management SDK, enabling app administrators to dissolve live rooms programmatically. It supports JSON requests with parameters including sdkappid, admin identifier, usersig, and RoomId. This API helps manage room lifecycle by allowing room dissolution and supports a maximum call rate of 200 queries per second. The response provides detailed status and room statistics. Additionally, the live room auto-destroy mechanism can be configured to automatically disband rooms based on inactivity or owner disconnection, enhancing resource management and user experience. - [Get Room Metadata](https://pre.trtc.io/document/64374.md): The Get Room Metadata API is a Chat platform interface that enables app administrators to retrieve custom metadata for rooms. It requires authentication parameters including sdkappid, identifier, and usersig, and supports JSON formatted requests. The API returns detailed room metadata along with status and error information, supporting up to 200 queries per second. This documentation covers request parameters, response structure, and error codes to facilitate integration and troubleshooting. - [Set Room Metadata](https://pre.trtc.io/document/64375.md): The Set Room Metadata API allows app administrators to manage room metadata within Tencent RTC. This RESTful API supports setting up to 10 metadata keys per room, with individual key lengths limited to 50 bytes and values up to 2KB, while the total size of all values cannot exceed 16KB. The API accepts JSON requests and returns detailed response packets including status, error codes, and unique request IDs. It supports a maximum calling frequency of 200 queries per second and provides specific error codes for effective troubleshooting. - [Delete Room Metadata](https://pre.trtc.io/document/64376.md): The Delete Room Metadata API enables app administrators to remove specific metadata keys from a room within the Tencent RTC platform. This RESTful API requires authentication parameters including sdkappid, identifier, and usersig, and supports JSON formatted requests. It is designed for administrators managing room metadata with a maximum call frequency of 200 requests per second. The API response provides detailed status and error codes to facilitate precise error handling and troubleshooting. - [Get Room Statistics](https://pre.trtc.io/document/80421.md): The Get Room Statistics API is a Tencent RTC REST API that allows application administrators to retrieve detailed interaction statistics for a specific room. It provides data such as total viewers, gifts sent, gift coin values, unique gift senders, likes received, and message counts. This API is designed for use in scenarios like operation consoles and post-stream data dashboards, enabling effective monitoring and analysis of room engagement metrics via JSON requests with a rate limit of 100 requests per second. - [Muting Members](https://pre.trtc.io/document/66969.md): The Mute Member API is a RESTful interface for app administrators to mute or unmute members within chat rooms. It supports JSON request and response formats and enforces a maximum calling frequency of 200 queries per second. This API requires parameters such as sdkappid, administrator identifier, and user signature, enabling precise control over member audio permissions. Detailed error codes and messages assist in troubleshooting API call issues. - [Get Muted Member List](https://pre.trtc.io/document/69894.md): The Get Muted Member List API is part of the Chat service API suite, enabling app administrators to query muted members within a chat room. It requires administrator credentials and supports JSON request format. The API returns mute status details including muted user IDs and expiration timestamps, facilitating effective room moderation. It also provides error codes for diagnosing issues during API calls. - [Get Room Member List](https://pre.trtc.io/document/66908.md): The Get Room Member List API is a REST API provided by Tencent RTC that allows app administrators to retrieve the list of members in a specified room. It supports pagination and returns up to 1000 members per request when the room size is large. This API is designed for administrators to monitor and manage room membership efficiently, with a maximum calling frequency of 200 queries per second. The response includes detailed status codes and error messages to facilitate troubleshooting. - [Banning Room Members](https://pre.trtc.io/document/63407.md): The Ban Room Members API allows an App Administrator to block users from entering a room for a specified duration. This API is part of the Chat platform and supports managing room membership by enforcing bans with reasons and time limits. It includes detailed request parameters, sample request and response packets, and error codes to facilitate integration and troubleshooting. - [Get Banned Member List](https://pre.trtc.io/document/63408.md): The Get Banned Member List API is a Chat service interface that allows App Administrators to retrieve the list of blocked members in a specified room. It supports pagination through Offset and Limit parameters and returns detailed information including banned member accounts and ban expiration times. This API is designed for administrators to manage user bans effectively with a maximum call frequency of 200 queries per second. Error codes are provided to assist in diagnosing issues during API calls. - [Get Administrator List](https://pre.trtc.io/document/63409.md): The Get Administrator List API allows an App Administrator to retrieve the list of room administrators in a chat room. This API is part of the Chat platform and requires parameters such as sdkappid, administrator identifier, usersig, and room ID. It supports JSON request format and returns detailed response fields including status, error codes, and the administrator list. The API is designed for administrators managing chat rooms and supports up to 200 calls per second. - [Unbanning Room Members](https://pre.trtc.io/document/63410.md): The Unbanning Room Members API is a RESTful interface designed for App Administrators to unblock members in chat rooms. It supports JSON requests to specify the room and members to be unbanned, with a maximum of 20 members per call and a rate limit of 200 calls per second. The API returns detailed response fields including action status, error codes, and unique request IDs to facilitate error handling and troubleshooting. - [Modify Administrator](https://pre.trtc.io/document/63411.md): The Modify Administrator API is part of the Chat platform SDK, enabling App Administrators to add or remove room administrators. It supports up to 5 administrators per room and requires authentication parameters such as sdkappid, identifier, and usersig. The API handles requests at a maximum frequency of 200 calls per second and returns detailed response fields including status and error codes to facilitate effective management of room administrators. - [Change Owner](https://pre.trtc.io/document/72534.md): The Change Owner API is a RESTful interface provided by Tencent RTC that enables App administrators to modify the owner of a room. It requires authentication parameters including sdkappid, administrator identifier, and usersig, and supports JSON formatted requests and responses. This API is designed for use by app admins to manage room ownership efficiently, with a maximum call frequency of 200 requests per second. The response includes detailed status and error codes to facilitate troubleshooting. - [Importing a Single Account](https://pre.trtc.io/document/34953.md): The Account Import API is a RESTful API in the Chat service that allows importing an app-owned account and creating an internal ID to enable the account to use Chat. It is designed for app administrators to manage user accounts by providing parameters like sdkappid, identifier, usersig, and supports up to 200 calls per second. The API returns detailed response fields and error codes to facilitate integration and troubleshooting. - [Importing Multiple Accounts](https://pre.trtc.io/document/34954.md): The Multi-Account Import API of the Chat SDK allows batch importing of up to 100 app-owned user accounts, creating internal IDs to enable Chat services. This API supports updating existing accounts with new user information such as nickname and avatar URL. It accepts JSON-formatted requests and provides detailed response structures including error codes for effective integration and troubleshooting. The API supports multiple regional endpoints and enforces a maximum call frequency of 100 requests per second. - [Deleting Accounts](https://pre.trtc.io/document/34955.md): The Chat Account Deletion API is part of the Chat SDK, enabling developers to programmatically delete user accounts and their associated data such as contacts, profiles, groups, and sessions. This API supports batch deletion of up to 100 accounts per request with a maximum call frequency of 100 calls per second. It is applicable to Chat trial editions by default and must be enabled for other editions like TRTC and Enterprise via the console. The API requires HTTPS POST requests with parameters including sdkappid, admin identifier, user signature, and content type. Detailed response information and error codes help developers handle deletion results effectively. - [Querying Accounts](https://pre.trtc.io/document/34956.md): The Account Query API in the Chat SDK allows developers to check if app-owned accounts have been imported, supporting batch queries of up to 100 accounts per request. It is designed for app administrators to verify account import status efficiently with a call frequency limit of 100 requests per second. The API provides detailed response information including action status, error codes, and account import states to facilitate integration and debugging. - [Setting Profiles](https://pre.trtc.io/document/34916.md): The Profile Setting API of Tencent Cloud Chat SDK enables developers to set both standard and custom profile fields for users. It supports JSON formatted requests with parameters including sdkappid, identifier, usersig, and others, and allows up to 200 calls per second. The API returns detailed response fields and specific error codes to facilitate integration and troubleshooting across multiple regional endpoints. - [Pulling Profiles](https://pre.trtc.io/document/34917.md): The Pulling Profiles API is a Chat service API under Tencent RTC that enables developers to retrieve standard and custom profile fields of friends and other users. It supports batch requests for up to 100 users per call to ensure efficient data retrieval and avoid response failures. Key parameters include sdkappid, identifier, usersig, and contenttype, with a maximum call frequency of 200 calls per second. This API is essential for applications requiring user profile information management. - [Get the Seat List](https://pre.trtc.io/document/64427.md): The Get the Seat List API is a RESTful interface for app administrators to obtain the list of seats in a chat room. It requires authentication parameters including SDKAppID and user signature, supports JSON request format, and returns detailed seat information such as seat index, occupant account, and seat status flags. This API supports up to 200 calls per second and provides error codes for troubleshooting seat list retrieval issues. - [Pick User on the Seat](https://pre.trtc.io/document/64428.md): The Pick User on the Seat API in Tencent RTC Chat SDK enables app administrators to assign room members to specific seat positions. This API supports JSON requests with parameters like RoomId, Member_Account, and Index, and returns detailed response data including error codes for troubleshooting. It is designed for real-time seat management in chat rooms and supports up to 200 calls per second. - [Kick User off the Seat](https://pre.trtc.io/document/64429.md): The Kick User off the Seat API is a RESTful HTTP interface provided by Tencent RTC that enables app administrators to remove members from the seat in a room. This API requires authentication parameters such as sdkappid, identifier, and usersig, and supports a maximum calling frequency of 200 times per second. It returns detailed JSON responses including error codes and messages to indicate the success or failure of the request. The API is designed for managing seat occupancy in real-time communication rooms. - [Lock the Seat](https://pre.trtc.io/document/64430.md): The Lock Seat API in Tencent RTC enables app administrators to lock specific seat positions within a room, preventing users from occupying them. This API supports parameters to disable video and audio streams for the locked seat and ensures that any current occupant is removed before locking. It uses RESTful HTTP requests with JSON payloads and returns detailed response information including error codes and request IDs for troubleshooting. - [Switch Seat(New version)](https://pre.trtc.io/document/72685.md): The Switch Seat API is part of the Tencent RTC SDK that enables app administrators to move on-mic users to different seats within a room. It supports operations such as forced moves, seat exchanges, and automatic unlocks triggered by muting. This API is designed for the new version of the Moving Mic feature and requires administrator credentials for authentication. It provides detailed request parameters, response payloads, and error codes to facilitate integration and troubleshooting. - [Switch Seat(Old version)](https://pre.trtc.io/document/72552.md): The Switch Seat API in the Chat service enables app administrators to move users to designated empty microphone slots within a room. This API requires administrator credentials and a valid UserSig for authentication. It supports JSON request format and allows up to 200 calls per second. The response includes detailed status information, error codes, and a unique request identifier to facilitate troubleshooting. - [Send Normal Message](https://pre.trtc.io/document/74353.md): The Send Normal Message API in the Chat service enables application administrators to send regular text messages via HTTP REST calls. This API requires parameters including sdkappid, admin identifier, usersig, and message content formatted in JSON. It supports custom data fields and message priority settings, with a maximum call rate of 200 requests per second. The response provides status and error codes to confirm message delivery results. - [Send Custom Message](https://pre.trtc.io/document/74354.md): The Send Custom Message API is part of the Chat service SDK, enabling application administrators to send custom messages programmatically. It supports JSON request formats with parameters including RoomId, Sender_Account, BusinessId, and message content. This API is designed for use by app admins to facilitate customized messaging with a maximum call frequency of 200 times per second. The response includes status codes, timestamps, and message sequence identifiers to track message delivery and errors. - [Message Formats](https://pre.trtc.io/document/74355.md): The Message Formats guide details the structure of MsgBody in Tencent RTC Chat, which supports multiple message elements within a single message. It explains the TIMMsgElement format, including types like text, location, emoji, custom, voice, image, file, and video messages. This overview is intended for developers integrating Tencent RTC Chat to understand how to compose and parse complex multi-element messages effectively. - [Create Battle](https://pre.trtc.io/document/68254.md): The CreateBattle API is a RESTful interface for App administrators to initiate battles between rooms in the live engine environment. It supports JSON requests with parameters including caller room ID, callee room IDs, and battle duration. The API returns detailed results and error codes to indicate success or failure. It is designed for applications requiring real-time room battle management and supports up to 200 calls per second. - [Set Battle Score](https://pre.trtc.io/document/68255.md): The Set Battle Score API is part of the Tencent RTC HTTP PK service, enabling app administrators to set or update scores for rooms involved in a Battle. This API supports two operation types: accumulating scores or overwriting existing scores. It requires parameters including BattleId, OpType, and a list of room scores. The API returns detailed response information including error codes and operation results, facilitating real-time score management in interactive live scenarios. - [Obtain Battle Information](https://pre.trtc.io/document/68256.md): The Get Battle Information API is part of the Chat platform API that enables app administrators to retrieve detailed information about battles. This API requires authentication via app admin credentials and supports JSON request format. It provides key battle data including duration, start and end times, status, and room scores. The API handles up to 200 calls per second and returns structured error codes for troubleshooting. - [Add Room Robot](https://pre.trtc.io/document/69079.md): The Add Room Robot API in the Live application SDK enables app administrators to add chatbots to rooms by sending structured requests with required parameters such as sdkappid, identifier, and usersig. It supports JSON format requests including room ID and robot account list, with a maximum calling frequency of 100 times per second. The API returns detailed response information including action status, error codes, and unique request IDs to facilitate troubleshooting and integration. - [Delete Room Robot](https://pre.trtc.io/document/69080.md): The Delete Room Robot API in the Live application SDK enables app administrators to remove robots from specified rooms. This API requires authentication via an administrator account and supports JSON request format with a maximum call frequency of 100 times per second. It provides detailed response fields to indicate success or failure and includes specific error codes for troubleshooting. - [Get Room Robot](https://pre.trtc.io/document/69081.md): The Get Room Robot API in the Live Application SDK enables app administrators to obtain the list of robots present in a specified room. This RESTful API requires parameters such as SDKAppID, administrator identifier, user signature, and room ID. It supports JSON request and response formats and enforces a maximum calling frequency of 100 requests per second. The API returns detailed response fields including action status, error codes, unique request ID, and the robot account list, facilitating effective management of live room robot participants. - [Gift System Configuration Guide](https://pre.trtc.io/document/72844.md): The Default Gift Config is a component of the gift system SDK that manages gift data, categorization, relationships, and multilingual support. It is designed for applications using TUILiveKit trial or large-scale live stream versions, enabling structured gift management through unique identifiers and supporting internationalization. The configuration process involves adding gifts and categories, establishing their relationships, and optionally adding language information for global use. - [Default Gift Config](https://pre.trtc.io/document/74360.md): The Default Gift Config API allows app administrators to set default gift information with 3 categories and 15 gifts. This API requires authentication parameters including sdkappid, identifier, and usersig, and supports JSON request format. It enforces a maximum call frequency of once every 10 seconds and returns detailed response fields for processing status and error handling. This reference covers request parameters, sample requests, response structure, and error codes to assist developers in integrating default gift configuration functionality. - [Add Gift](https://pre.trtc.io/document/72845.md): The Add Gift API is a RESTful interface designed for app administrators to add gift information within the Tencent RTC live engine HTTP service. It requires authentication parameters such as sdkappid, admin identifier, and usersig, and supports JSON formatted requests. This API enables management of gift details including gift ID, icon URL, resource URL, virtual currency price, and optional metadata. The API enforces a maximum call frequency of one request per second and returns structured responses with error codes and status messages to facilitate integration and error handling. - [Get Gift](https://pre.trtc.io/document/72846.md): The Get Gift API in the Chat SDK allows App administrators to query detailed gift information by sending HTTP requests with required parameters such as sdkappid, identifier, and usersig. This API supports JSON format requests and returns comprehensive gift data including IDs, icons, resource URLs, prices, levels, and descriptions. It enforces a maximum call frequency of one request per second and provides specific error codes for troubleshooting. - [Delete Gift](https://pre.trtc.io/document/72847.md): The Delete Gift API is a REST API that enables App administrators to remove specified gift information from their application. It supports secure calls with required parameters including SDKAppID, administrator credentials, and a JSON request body specifying the gift ID. The API confirms successful deletion or indicates if the gift does not exist, returning detailed status and error codes to assist in troubleshooting. It is designed for controlled usage with a maximum call frequency of one request per second. - [Add Gift Category](https://pre.trtc.io/document/72848.md): The Add Gift Category API in the Chat SDK enables app administrators to add gift classification information by sending JSON-formatted requests. It requires administrator authentication via user signature and supports parameters like CategoryId, DefaultName, and optional ExtensionInfo. The API returns detailed response fields including action status, error codes, and a unique request ID to assist in troubleshooting. It enforces a maximum call frequency of one request per second and is designed for managing gift categories within chat applications. - [Get Gift Category](https://pre.trtc.io/document/72849.md): The Get Gift Category API in the Chat service enables App administrators to retrieve detailed information about specified gift categories. This API requires authentication via SDKAppID and administrator user signature, supports JSON format requests, and enforces a maximum call frequency of one request per second. The response provides gift category identifiers, default names, descriptions, and custom extension information, along with error codes for troubleshooting. - [Delete Gift Category](https://pre.trtc.io/document/72850.md): The Delete Gift Category API in the Chat service enables App administrators to remove specified gift classification information. This RESTful API requires administrator credentials and supports JSON request format. It ensures deletion of the gift category along with related language and gift relationship data. The API supports a maximum calling frequency of once per second and returns detailed response fields including error codes and request IDs for effective troubleshooting. - [Add Gift Category Relationships](https://pre.trtc.io/document/72851.md): The Add Gift Category Relationships API enables App administrators to associate specified gift categories with gifts using a JSON request format. This API is designed for app administrators to manage gift category relationships efficiently by sending requests with required parameters such as SDKAppID, user signature, and category and gift IDs. It supports a maximum calling frequency of one request per second and provides detailed response information including success status and error codes to facilitate integration and troubleshooting. - [Delete Gift Category Relationships](https://pre.trtc.io/document/72852.md): The Delete Gift Category Relationships API enables app administrators to remove specified gift-category associations within the Tencent RTC environment. It supports JSON-formatted requests and returns success even if the specified relationships do not exist. This API is designed for use by app administrators to manage gift categories efficiently, with a maximum call frequency of one request per second. The response includes detailed error codes to facilitate troubleshooting. - [Get Gift Category Relationships](https://pre.trtc.io/document/72853.md): The Get Gift Category Relationships API is part of the Chat API suite, enabling App administrators to retrieve gift relationships within a specified category. This API requires authentication parameters including sdkappid, identifier, and usersig, and supports JSON request format. It provides detailed response data such as gift category IDs and associated gift lists, along with comprehensive error codes for troubleshooting. The API is designed for use by App administrators to manage gift categories efficiently with a maximum call frequency of once per second. - [Add Gift Language Infomation](https://pre.trtc.io/document/72854.md): The Add Gift Language Information API is a RESTful interface that enables App administrators to add or modify gift language details within the Tencent RTC live engine HTTP service. It requires authentication parameters such as sdkappid and usersig, supports multiple language types, and enforces a call frequency limit of one request per second. The API returns structured responses including status and error codes to facilitate integration and troubleshooting. - [Get Gift Language Infomation](https://pre.trtc.io/document/72855.md): The Get Gift Language API is a RESTful interface designed for App administrators to retrieve gift language information. It requires specific parameters including SDKAppID, administrator identifier, user signature, and supports JSON request format. The API enforces a maximum call frequency of one request per second and returns detailed response data including gift name and description. Error codes and messages are provided to assist in troubleshooting request issues. - [Delete Gift Language Infomation](https://pre.trtc.io/document/72856.md): The Delete Gift Language Information API is a RESTful interface that enables app administrators to remove specified gift language data within the Tencent RTC ecosystem. It requires authentication parameters including sdkappid, administrator identifier, and usersig, and supports multiple language types such as English and Chinese variants. The API ensures idempotent deletion by returning success even if the gift language info does not exist. It enforces a maximum call frequency of one request per second and provides detailed error codes and messages to facilitate troubleshooting. - [Add Gift Category Language Infomation](https://pre.trtc.io/document/72857.md): The Add Gift Category Language Information API is part of the Chat API that enables app administrators to add or update language-specific details for gift categories. It supports multiple languages including English and Chinese variants, allowing customization of gift category names and descriptions. This API requires authentication via an administrator account and enforces a maximum call frequency of one request per second. The response provides detailed error codes and status to facilitate integration and troubleshooting. - [Get Gift Category Language Infomation](https://pre.trtc.io/document/72858.md): The GetGiftCategoryLanguage API is part of the Chat service API that enables app administrators to retrieve language-specific information for gift categories. It requires parameters such as SDKAppID, administrator identifier, and user signature to authenticate the request. The API returns the gift category name and description in supported languages including English and Chinese variants. It supports a maximum call frequency of one request per second and provides detailed error codes for troubleshooting. - [Delete Gift Category Language Infomation](https://pre.trtc.io/document/72859.md): The Delete Gift Category Language Information API is part of the Tencent RTC REST API suite, enabling App administrators to remove specified gift category language data. This API supports parameters such as sdkappid, identifier, usersig, and requires JSON formatted requests. It handles languages including English, Simplified Chinese, and Traditional Chinese. The API ensures secure and controlled access with a maximum call frequency of one request per second and provides comprehensive response details and error codes for effective integration and troubleshooting. - [Get Gift Statistics](https://pre.trtc.io/document/72557.md): The Get Gift Statistics API in the Chat service enables application administrators to retrieve detailed gift statistics for specific users. It requires the SDKAppID assigned by the Chat console and an admin user signature for authentication. The API supports JSON format requests and provides key metrics such as total gift quantity, total gift value, and the number of gift senders. This documentation details the request parameters, response structure, error codes, and usage limits including a maximum call frequency of 200 times per second. - [Send Gift](https://pre.trtc.io/document/72556.md): The Send Gift API is part of the Chat REST API that enables an application administrator to send virtual gifts within a chat room. This API requires authentication via the admin's UserSig and supports parameters including room ID, gift ID, gift count, sender, and recipient list. It handles up to 200 calls per second and returns detailed response status and error codes to facilitate integration and troubleshooting. - [Webhooks Overview](https://pre.trtc.io/document/64412.md): LiveKit Webhooks SDK enables app developers to configure webhook URLs via REST API to receive event notifications securely. It supports HTTP/HTTPS POST requests with parameters like SdkAppId and WebhookCommand. The SDK emphasizes security by recommending HTTPS and providing webhook authentication using SHA256 signatures to verify request authenticity and prevent replay attacks. This overview also covers common webhook failure causes such as DNS issues, firewall restrictions, and server errors, helping developers ensure reliable webhook integration. - [Webhooks Command List](https://pre.trtc.io/document/64413.md): The Webhooks Command List provides detailed webhook command words for different event types in Tencent RTC, including room, user, mic, battle, gift, message, following, and recording related events. This API reference is designed for developers integrating real-time communication features who need to handle event callbacks effectively within their applications. - [Console Webhook Configuration](https://pre.trtc.io/document/74157.md): TencentRTC Live console provides a guide to configure webhook URLs and manage event webhooks. This quickstart helps users log in, select applications, and set up webhook URLs with correct formatting, as well as enable or disable event webhooks for social interaction features. Key steps include editing the webhook URL, confirming changes, and managing webhook switches to meet business requirements. - [Query Webhook Configuration](https://pre.trtc.io/document/64418.md): The Query Webhook Configuration API is part of the Chat SDK, enabling app administrators to retrieve webhook settings by specifying parameters like sdkappid, identifier, and usersig. This API supports up to 200 queries per second and returns detailed response fields including webhook URL and callback commands. It is designed for administrators managing webhook integrations within Tencent RTC Chat applications. - [Update Webhook Configuration](https://pre.trtc.io/document/64419.md) - [Create Webhook Configuration](https://pre.trtc.io/document/64420.md): The Create Webhook Configuration API in Tencent Cloud Chat SDK allows app administrators to set webhook callback URLs and specify callback command lists. This API requires parameters including sdkappid, administrator identifier, usersig, random number, and content type. It supports up to 200 queries per second and returns detailed response fields such as ActionStatus, ErrorCode, ErrorInfo, and RequestId for request tracking and error handling. This documentation provides parameter descriptions, sample requests and responses, and error code explanations. - [Delete Webhook Configuration](https://pre.trtc.io/document/64421.md): The Delete Webhook Configuration API allows App Administrators to remove webhook settings on the Chat platform. This API requires authentication parameters including sdkappid, identifier, and usersig, supports JSON request format, and enforces a maximum call frequency of 200 queries per second. The response includes detailed status and error information to assist in troubleshooting and integration. - [Set Webhook Authentication Token​​](https://pre.trtc.io/document/69528.md): The Set Webhook Authentication Token API allows app administrators to create or update the webhook authentication token for their applications. This API supports JSON request and response formats and requires parameters including sdkappid, identifier, usersig, random, and contenttype. It enables secure webhook communication by managing token values and activation status. The API supports up to 200 calls per second and returns detailed error codes in the response body to facilitate troubleshooting. - [Query Webhook Authentication Token​​](https://pre.trtc.io/document/69529.md): The Query Webhook Authentication Token API allows app administrators to retrieve the webhook authentication token used for securing webhook requests. This API is part of the Tencent RTC platform and requires parameters including sdkappid, identifier, usersig, random, and contenttype. It supports up to 200 calls per second and returns detailed response fields such as Token and IsTokenEnable to indicate the token status. Error handling is managed via ErrorCode and ErrorInfo in the response body. - [Delete Webhook Authentication Token​​](https://pre.trtc.io/document/69530.md): The Delete Webhook Authentication Token API allows App Administrators to remove the webhook authentication token configuration. This API requires parameters including sdkappid, identifier, usersig, random, and contenttype, and supports up to 200 calls per second. The response provides detailed status information through fields such as ActionStatus, ErrorCode, ErrorInfo, and RequestId, enabling effective management and troubleshooting of webhook token deletion. - [Webhook After Room Creation](https://pre.trtc.io/document/64422.md): The Webhook After Room Creation API is part of Tencent RTC's webhook protocol that enables app backends to receive real-time notifications when users or administrators successfully create rooms. This API uses HTTPS POST requests to deliver detailed room information such as room ID, name, owner, member limits, microphone settings, and custom fields. It supports data synchronization and operational triggers immediately after room creation, requiring proper webhook URL configuration and SDKAppID verification to ensure secure and accurate processing. - [Webhook After Room Destroyed](https://pre.trtc.io/document/64423.md): The Webhook After Room Destroyed is a real-time monitoring SDK feature that enables app backends to track room dissolution events immediately after a room is destroyed. It is designed for developers who need to log or synchronize room destruction data with other systems. This webhook sends HTTPS POST requests containing detailed information such as operator account, room ID, dissolution type, and room metadata. It requires configuration of the webhook URL and protocol toggling to function properly. - [Webhook After Room Update](https://pre.trtc.io/document/67938.md): The Webhook After Room Update API is a Tencent RTC webhook service that enables app backends to receive real-time notifications of room information changes. It is designed for app developers who need to log or sync room updates triggered by users or administrators. The webhook sends HTTPS POST requests containing detailed room data after successful updates, and requires backend verification of SDKAppID. This API supports parameters such as room ID, room name, member count, and custom fields, facilitating seamless integration and synchronization with backend systems. - [Creating Room Reaches 70% Alert Callback](https://pre.trtc.io/document/70485.md): Creating Room Reaches 70% Alert Callback is a Tencent RTC feature that enables the App backend to monitor room creation counts by receiving HTTP POST callbacks from the Live backend. This callback notifies when the number of created rooms reaches 70% of the maximum allowed, helping app administrators track usage and manage capacity. To use this feature, the App backend must configure the callback URL and enable the callback switch, then verify SDKAppID in incoming requests. The callback includes detailed parameters such as current room count, maximum room count, and event timestamp. - [Webhook After Room Metadata Deleted](https://pre.trtc.io/document/68223.md): The Webhook After Room Metadata Deleted is a Tencent RTC API that enables app servers to receive notifications when room metadata is deleted. It supports HTTPS POST requests containing details like operator account, room ID, and deleted keys. This API helps app developers monitor metadata deletion events triggered by users or administrators and ensures secure verification of SDKAppID. The response mechanism allows the app server to acknowledge processing results. - [Webhook After Room Metadata Set](https://pre.trtc.io/document/68222.md): The Webhook After Room Metadata Set API is a Tencent RTC webhook service that enables app servers to monitor real-time changes to room metadata. It is designed for app developers and administrators who need to track metadata updates triggered by users or admin actions. The webhook sends HTTPS POST requests with detailed metadata information after successful metadata updates, allowing seamless synchronization and event handling. Key parameters include SDKAppID verification, operator account, room ID, metadata key-value pairs, and event timestamp. - [Webhook After Room Member Status Changed](https://pre.trtc.io/document/64424.md): The Webhook for Room Member Status Changes is a Tencent RTC service that enables app backends to receive real-time notifications about users' online and offline status changes within a room. It supports scenarios such as users entering or leaving rooms, heartbeat interruptions or recoveries, and administrative kicks. By configuring the webhook URL and enabling the protocol, developers can integrate this webhook to monitor user presence and respond to state changes promptly. - [Webhook After Room Owner Change](https://pre.trtc.io/document/72553.md): The Webhook After Room Owner Change API is part of the live chat SDK that notifies the app backend when a room owner is changed. It is designed for app developers to receive real-time updates about ownership changes triggered by users or admins. The callback uses HTTPS POST requests and requires verification of the SDKAppID. This API provides key parameters such as RoomId, CurrentOwner_Account, OriginalOwner_Account, and Operator_Account, enabling backend synchronization and response handling. - [Webhook After Room Admin Change](https://pre.trtc.io/document/72554.md): The Webhook After Room Admin Change API is a callback service that enables the App backend to receive notifications about modifications to room administrators. It supports scenarios where admins are changed via client or REST API, and delivers data through HTTPS POST requests. This API provides detailed request and response packet structures, including parameters such as RoomId, Admin_Account list, operation type, and operator account, allowing backend systems to synchronize admin changes effectively. - [Webhook After Seat List Changed](https://pre.trtc.io/document/64425.md): The Mic.CallbackAfterSeatInfoChanged webhook API enables app backends to receive real-time updates on microphone position list changes within Tencent RTC. This API is designed for applications that need to track user microphone status changes such as mute/unmute actions and microphone position locks. The webhook sends HTTPS POST requests with JSON payloads containing detailed microphone seat information. App backends must validate the SDKAppID and respond with a JSON packet indicating processing results. This API facilitates real-time synchronization of microphone state in interactive audio scenarios. - [Webhook After Creating Battle](https://pre.trtc.io/document/68259.md): The Webhook After Creating Battle API is a Tencent RTC webhook service that enables app servers to receive real-time notifications when a user creates a battle. It supports HTTPS POST requests containing detailed battle data such as battle ID, room IDs, duration, and participant information. This API is designed for app developers who need to synchronize battle creation events and handle related workflows by verifying the SDKAppID and processing the JSON payload. The documentation includes request URL format, parameter descriptions, sample request and response packets, and field explanations to facilitate integration. - [Webhook After Starting Battle](https://pre.trtc.io/document/68260.md): The Webhook After Creating Battle API in Tencent RTC allows app servers to monitor when a battle starts by receiving HTTPS POST requests with detailed battle information. This API is intended for developers integrating battle start notifications, providing parameters such as battle ID, duration, start time, and participant details. The documentation includes request URL format, parameter descriptions, sample request and response packets, and verification requirements to ensure secure and accurate webhook handling. - [Webhook After Ending Battle](https://pre.trtc.io/document/68261.md): The Webhook After Ending Battle API is a Tencent RTC webhook service that notifies the app server when a battle ends. It is designed for app developers to monitor battle lifecycle events by receiving HTTPS POST requests containing detailed battle data. This API requires configuration of the webhook URL and enabling the webhook switch. The request includes parameters such as SDKAppID and CallbackCommand, and provides comprehensive battle details like BattleId, duration, start and end times, operation type, and room information. The app server must verify the SDKAppID and respond with processing status to ensure proper synchronization. - [Webhook before Sending Gift](https://pre.trtc.io/document/72210.md): The Webhook Before Sending Gift is an API callback in the Tencent RTC live streaming service that allows the app backend to verify and control gift sending actions before they occur. It is triggered via an HTTPS POST request containing gift and user details, enabling the app backend to approve or block gift transactions by responding with specific status codes. This API is designed for app backends to integrate gift verification logic in real-time live streaming scenarios. - [Before Group Message Is Sent](https://pre.trtc.io/document/74347.md): The Before Room Message Is Sent webhook event is a real-time monitoring SDK feature that enables app backends to intercept and verify room messages before they are sent to members. It is designed for applications requiring message logging, synchronization, or blocking capabilities. This webhook triggers an HTTPS POST request containing detailed message data and sender information, allowing backend systems to enforce message control policies securely within a two-second timeout window. - [After Group Message Is Sent](https://pre.trtc.io/document/74348.md): The After Room Message Is Sent webhook event is part of the Tencent RTC Chat SDK, designed to notify the app backend in real time when a room message is sent successfully. It enables backend systems to synchronize message data securely by receiving HTTPS POST callbacks containing detailed message information. This webhook supports scenarios where messages are sent by app users or administrators via RESTful APIs, providing essential parameters such as message ID, sender, room ID, and timestamps to facilitate message tracking and processing. - [After a User Is Followed](https://pre.trtc.io/document/74356.md): The After a User Is Followed webhook is a Chat SDK feature that allows the app backend to receive real-time notifications when a user successfully follows another user. This webhook is triggered by follow actions initiated either through the client or via REST API. It requires configuring the webhook URL and enabling the webhook switch. The webhook sends an HTTPS POST request containing follow event data, including user IDs and timestamps, enabling apps to process follow events securely and efficiently. - [After a User Is Unfollowed](https://pre.trtc.io/document/74357.md): The User Unfollow Webhook is a Chat service feature that enables app backends to receive real-time notifications when users unfollow others. It supports HTTPS POST requests triggered upon successful unfollow actions initiated by users or administrators. This webhook requires configuring the webhook URL and enabling the feature in the Chat console. It provides essential parameters such as SDKAppID verification, user IDs involved, and event timestamps to help apps respond promptly and securely to unfollow events. - [After Recording Status Changes](https://pre.trtc.io/document/78428.md): The Recording Status Change Webhook is a real-time notification service within Tencent RTC that allows app backends to receive updates on recording status changes. It is designed for app developers who need to monitor live stream recording events by configuring a webhook URL and enabling the webhook switch. The webhook triggers HTTP POST requests after recording status changes, providing detailed event information including timestamps, user IDs, and task IDs, while ensuring security through SDKAppID verification. - [Overview](https://pre.trtc.io/document/56765.md): Tencent Real-Time Communication (TRTC) Application Overview provides detailed information on managing applications within the TRTC platform. It is designed for developers and administrators to view and modify application details such as SDKAppID, SDKSecretKey, application version, and service status. The guide explains how to access application information, update names and descriptions, understand service states including normal and disabled, and manage subscription plans to unlock additional features based on business needs. - [Creating Application](https://pre.trtc.io/document/39077.md): Tencent Real-Time Communication (TRTC) Console provides an application management SDK that enables users to create and manage multiple applications for distinct business projects. This guide explains how to create an application, including entering the application name, selecting the product and deployment region, and accessing key credentials like SDKAppID and SDKSecretKey. It also covers viewing and managing the application list with detailed information such as service status and deployment region, facilitating efficient project isolation and data management. - [Function Configuration](https://pre.trtc.io/document/39080.md): Function Configuration in Tencent RTC enables users to activate Relay to CDN, On-Cloud Recording, and advanced permission control for their applications. This guide provides step-by-step instructions to enable, configure, switch domain names, and disable these features, helping users manage audio and video streaming and recording efficiently with Tencent Cloud CSS integration. - [Callback Configuration](https://pre.trtc.io/document/39559.md): The Tencent RTC Event callback service SDK allows developers to configure webhook keys and URLs to receive real-time notifications of audio and video service events. This guide provides step-by-step instructions for setting up webhook configuration in the Tencent RTC console, including prerequisites and key actions to enable event callback notifications for room, media, recording, and relay events. - [Package Management](https://pre.trtc.io/document/56766.md): Tencent Real-Time Communication (TRTC) Package Management is a console-based feature that allows users to view and manage their package usage and subscriptions. It supports different package types including Free Trial and monthly packages, providing detailed usage statistics and purchase options. This overview helps users understand how to monitor package status, renew subscriptions, and take advantage of discount campaigns to optimize their audio and video service usage. - [Interactive Audio/Video](https://pre.trtc.io/document/39066.md): TRTC Interactive Audio/Video is a feature within the Tencent RTC console that offers real-time statistics and detailed consumption data for created applications. It is designed for developers and operators to monitor audio and video interaction usage, including paid and free usage, with data updated every five minutes. This helps users understand their application consumption and billing details accurately. - [On-Cloud Recording](https://pre.trtc.io/document/39067.md): Tencent Real-Time Communication On-Cloud Recording usage statistics provide detailed insights into cloud recording usage based on recording duration. This overview helps users understand how to view usage data in the TRTC console, including application selection and time period filtering. Data updates every 5 minutes with a delay of up to 180 minutes, and durations are rounded for billing accuracy. Billing details are accessible via the Billing Center. - [On-Cloud MixTranscoding](https://pre.trtc.io/document/44058.md): Tencent Real-Time Communication (TRTC) On-Cloud MixTranscoding consumption statistics provide detailed usage data for MCU cloud mixtranscoding services. This overview explains how users can view consumption details in the TRTC console, including data update frequency, usage duration calculation, and billing references. It is designed for developers and service users who need to monitor and manage their cloud-based mixed-stream transcoding consumption effectively. - [Relay to CDN](https://pre.trtc.io/document/56767.md): The TRTC Relay to CDN feature is a bypass push service within the Tencent RTC platform. It is designed for users who need to monitor and analyze bandwidth usage and billing details related to content delivery network relay. This overview explains how to access usage statistics, interpret peak bandwidth data in five-minute and daily intervals, and estimate monthly costs based on detailed logs, with actual charges confirmed via the Billing Center. - [Call List](https://pre.trtc.io/document/39069.md): Tencent RTC Call List is a monitoring dashboard feature that enables developers to view and analyze call details and user call statuses. It supports filtering calls by application, time period, room ID, or user ID, helping developers monitor call quality and user participation effectively. - [Call Details](https://pre.trtc.io/document/39070.md): The Call Details page in the Tencent RTC monitoring dashboard provides comprehensive information about a specific call room. It is designed for users managing or analyzing call sessions, offering key data such as call room metadata, user roles and activity, SDK versions, device and network types, and detailed statistics on data transmission from both receiver and sender perspectives. This overview helps in understanding call performance and user participation within a selected time range. - [End-to-End Details](https://pre.trtc.io/document/39071.md): Tencent RTC End-to-End Call Details provide comprehensive insights into data transmission between sender and receiver during audio and video calls. This overview helps users monitor network conditions and device performance, displaying detailed metrics such as video and audio packet loss, frame rates, resolutions, and control parameters. Accessible through the Tencent RTC Console, it supports troubleshooting and optimizing call quality by visualizing multi-dimensional data for both sender and receiver. - [Real-Time Monitoring](https://pre.trtc.io/document/52069.md): Tencent Real-Time Communication (TRTC) real-time monitoring SDK provides a multi-dimensional, visualized platform to track application performance metrics such as online users, rooms, and quality indicators including video and audio stutter rates. Designed for developers and operators, this monitoring service enables timely detection and troubleshooting of issues with data updated every 10 to 20 seconds. Features include pausing data views, detailed scale and quality metrics, and downloadable room data, accessible through the Tencent RTC Console. - [Data Insights](https://pre.trtc.io/document/67828.md): The Data Insights on RTC Analytics Data Dashboard is a paid SDK feature designed for application operators to monitor and analyze business operation scale and call quality metrics. It provides key operational metrics such as user counts, room counts, peak hour statistics, and multi-dimensional quality analysis including video and audio stutter rates. Users can filter data by application and time range, view trend charts, and export detailed reports to gain timely insights into call performance and operational trends. - [UserSig Generation and Verification](https://pre.trtc.io/document/39074.md): UserSig Generation and Verification is a guide for using the TRTC console's Signature (UserSig) Generator and Verifier tools. It is designed for developers to quickly generate UserSig for testing purposes and verify its validity to ensure secure communication by preventing key leakage and unauthorized access. The guide includes step-by-step instructions for generating UserSig with a 180-day expiration and verifying UserSig by inputting UserID and signature details. - [RTMP Address Generator](https://pre.trtc.io/document/67774.md): The TRTC console provides an RTMP Address Generator tool designed for testing streaming room entry. This quickstart guide helps users generate RTMP streaming addresses by selecting their application, entering the room name and user ID, and generating the address. It is intended for developers to quickly test streaming setups before deploying secure backend address generation for official use. - [Live Recording](https://pre.trtc.io/document/77024.md): TRTC Live provides a live recording SDK that enables capturing and storing audio and video from live streaming rooms. This guide explains how to configure recording storage, enable recording for all rooms or individual rooms, and manage recording parameters during room creation. It helps developers quickly set up live recording for playback, evidence collection, and quality assurance scenarios on supported live rooms with isUnlimitedRoomEnabled enabled. - [Quick Start (Vue3)](https://pre.trtc.io/document/74097.md): The Live Streaming Management System SDK offers comprehensive live streaming operations capabilities including live monitoring, room management, gift configuration, and content moderation for Web Vue Desktop Browser. This quick start guide helps developers set up the environment, activate services, download the project, configure the server and frontend, and deploy the system efficiently. Key steps include environment preparation, service activation, project cloning, server configuration, and frontend startup to enable rapid integration and testing. - [Quick Start (React)](https://pre.trtc.io/document/74096.md): The Live Streaming Management System is a web React desktop browser SDK designed to provide comprehensive live streaming operations capabilities. It targets operators and developers aiming to efficiently manage live rooms, monitor streams, configure gifts, and moderate content. This quick start guide covers environment setup, service activation, project download, server and frontend configuration, and deployment options to help users rapidly integrate and deploy the system. - [SDK Customization (Vue3)](https://pre.trtc.io/document/81896.md): TUILiveKit Manager Vue SDK is a live streaming management SDK designed for Vue 3 developers. It enables customization of the live streaming management console by providing core Hooks for live room, gift, and risk control management. This quick start guide covers environment setup, service activation, backend server configuration, dependency installation, and HTTP client initialization to help developers quickly integrate and customize live streaming features. - [SDK Customization (React)](https://pre.trtc.io/document/81897.md): TUILiveKit Manager React SDK is a live streaming management SDK designed for developers to customize live streaming consoles. It supports environment setup with Node.js and React, backend server configuration, dependency installation, and HTTP client initialization. Key features include core Hooks for live room, gift, and risk control management, enabling efficient live streaming operations. - [Set Up Live Streaming with TRTC Live](https://pre.trtc.io/document/78279.md): TRTC Live is an interactive live streaming SDK designed for social entertainment, e-commerce, and fitness scenarios. It supports Android, iOS, Flutter, Web, and Electron platforms, enabling developers to quickly integrate features such as live streaming, voice chat rooms, barrage messaging, gift sending, co-hosting, and room management. This guide provides step-by-step instructions for choosing integration options, setting up live streaming and viewing, and implementing interactive features to rapidly launch your live streaming business. - [Retail E-commerce Solution and Live Integration Guide](https://pre.trtc.io/document/78878.md): The Retail E-commerce Live Streaming Solution integrates Tencent RTC's Live and Chat SDKs to enable real-time audio and video interaction combined with online trading. Designed for developers, it addresses complex requirements including low-latency streaming, high concurrency communication, interactive messaging, and marketing event synchronization. The solution also includes advanced Beauty AR integration for enhanced anchor avatars and supports diverse business scenarios such as self-operated and cross-border e-commerce. It provides a comprehensive architecture covering live streaming, transaction management, marketing, customer service, and user domains to facilitate rapid and customizable e-commerce live streaming system development. - [Best Practices for Web3 and FinTech Solutions](https://pre.trtc.io/document/81451.md): The Web3 and FinTech Real-Time Interaction Solution is a comprehensive SDK and service suite designed for developers in the financial and blockchain sectors. It addresses key real-time interaction needs such as live streaming, instant messaging, transcription, and translation, leveraging Tencent RTC's TRTC, Chat, and Push capabilities. This solution offers a standardized architecture and best practices to build scalable, multilingual, and compliant live streaming and messaging systems, supporting scenarios like crypto exchanges, social wallets, and investment advisory communities. - [Privacy Policy](https://pre.trtc.io/document/48827.md): The Tencent Real-Time Communication (TRTC) Feature Privacy Policy outlines how personal information is collected, used, stored, and shared for users worldwide. It details data processing activities related to website visits, account registration, feature usage, and backend logs, ensuring compliance with legal bases such as legitimate interests and contractual obligations. This policy helps users understand data controllership, availability, and retention practices for the TRTC Feature. - [Data Processing And Security Agreement](https://pre.trtc.io/document/48828.md): The Tencent Real-Time Communication Data Processing and Security Agreement module outlines the handling and retention of personal and customer data related to the real-time communication feature. It applies to users leveraging this feature and details data processing purposes, service regions, sub-processors involved, data retention policies, and special conditions including end-user consent requirements to ensure compliance with relevant laws. ## Pricing - [Billing Overview](https://pre.trtc.io/document/64149.md): Tencent RTC Billing Overview provides detailed information on the prepaid and pay-as-you-go billing models for Tencent RTC services, including Call, Conference, Live, RTC-engine, Chat, and Beauty AR. This guide explains the available monthly subscription and annual top-up prepaid packages, automatic renewal policies, and pay-as-you-go billing for usage exceeding prepaid balances. It helps users understand billing classifications and choose the appropriate plan for their business scenarios. - [Starter Plan](https://pre.trtc.io/document/60294.md): Tencent Cloud Starter Plan is a subscription package designed for new users to access various Tencent Cloud products at a discounted rate for the first month. It supports multiple products such as Chat, RTC Engine, Call, Conference, Live, and Beauty AR, providing essential features with pay-as-you-go options and free trials. The plan is valid for one month from purchase and is limited to one purchase per product per account, helping new customers minimize initial project costs while exploring Tencent Cloud services. - [Package Purchase, Renewal and Upgrade](https://pre.trtc.io/document/74514.md): Tencent Real-Time Communication (Tencent RTC) provides a comprehensive guide for purchasing, renewing, and upgrading service packages through the Tencent RTC Console. This guide is intended for users managing TRTC products who need to understand billing options, manual and auto-renewal processes, and upgrade paths to access enhanced features. It includes step-by-step instructions for binding applications, selecting package versions, completing payments, enabling or disabling auto-renewal, and upgrading packages to higher versions without service interruption. - [Call Monthly Packages](https://pre.trtc.io/document/54632.md): TRTC Call (TUICallKit) is a multi-platform call SDK with a UI Kit that enables audio and video calling features including one-to-one and group calls. Designed for Android, iOS, web, and Flutter, it offers flexible billing through monthly packages and pay-as-you-go fees. This overview explains the cost structure, package usage rules, billing details, and a limited-time Starter Plan for new users to manage initial costs effectively. - [Conference Monthly Packages](https://pre.trtc.io/document/59409.md): TRTC Conference (TUIRoomKit) is a multi-person audio and video chat SDK designed for scenarios like business meetings, webinars, and online education. This overview explains the pricing structure including monthly package fees and pay-as-you-go charges, MAU calculation rules, and package validity. It also highlights a limited-time Starter Plan offering 10,000 free minutes for new users. The guide helps users understand cost management and billing details for TRTC Conference features across applications. - [Chat Monthly Package](https://pre.trtc.io/document/67650.md): Chat Monthly Package is a prepaid subscription service offering multiple plans such as Free, Standard, Pro, Pro Plus, and Enterprise tailored for app developers and businesses. It enables flexible billing per app with monthly active user quotas and concurrent connection limits. This overview explains billing rules, pricing, core quotas, and detailed feature comparisons to help users select the appropriate plan for their communication needs. - [RTC-Engine Monthly Packages](https://pre.trtc.io/document/56025.md): RTC-Engine monthly subscription packages provide prepaid access to audio/video call minutes and advanced TRTC features for individual applications. Designed for developers using TRTC applications, these packages unlock various service tiers including Free Trial, Lite, Standard, and Pro, each with different pricing, included minutes, and feature sets. The billing cycle spans one month from purchase, and a Starter Plan offers a special introductory offer for new users. Supported platforms include iOS, Android, Windows, Web, Electron, Flutter, and React Native. - [Beauty AR Web Monthly Packages](https://pre.trtc.io/document/60214.md): Beauty AR SDK Web&H5 is an augmented reality SDK offering three monthly subscription packages—Standard, Professional, and Advanced—that provide various beauty and AR capabilities such as filters, makeup, stickers, and virtual backgrounds. Designed for web and H5 platforms, it supports domain-bound licensing with options for absolute and wildcard domains. This pricing guide helps users choose the right package based on their business needs and explains billing details including license binding, renewal, and usage restrictions. - [Beauty AR Mobile Monthly Packages](https://pre.trtc.io/document/69949.md): The Beauty AR SDK for Mobile is a software development kit offering facial beautification and augmented reality effects, divided into Standard A series, Advanced S series, and Capabilities. It targets developers needing customizable beauty effects, stickers, makeup, and virtual backgrounds for mobile applications. This SDK supports flexible licensing options including monthly and annual purchases, providing scalable solutions for diverse beautification needs with detailed pricing and feature differentiation. - [RTC Analytics Monthly Packages](https://pre.trtc.io/document/54481.md): RTC Analytics Monthly Packages is a subscription-based monitoring dashboard service that offers Room Call Investigation, Real-Time Monitoring, and Data Analytics Dashboard capabilities. Designed for users needing detailed call quality analysis and real-time data insights, it supports Standard and Premium editions with different data retention and latency features. This overview explains the package features, billing standards, and subscription management steps including how to subscribe and cancel. - [RTC Engine Top-Up Package](https://pre.trtc.io/document/79594.md): The RTC Engine Top-Up Package is a prepaid usage minutes package for audio/video calls under the Tencent RTC platform. It is designed for users who have exhausted their free minutes or monthly packages, providing additional minutes valid for one year across all applications in the account. This package supports flexible billing with multiple stacking options and follows a clear deduction priority to manage usage efficiently. - [Billing of Chat Out-of-Package Usage](https://pre.trtc.io/document/67651.md): Tencent Cloud Chat Out-of-Package Usage Billing document provides detailed pricing information for on-demand features including overage monthly active users (MAU), community message delivery volume, text message translation, cloud search limited to the Singapore data center, cloud push, and server-side API rate-limit adjustments. This guide is designed for developers and businesses using Chat SDKs who need to understand billing beyond monthly plans, including free trial quotas and monthly postpaid charges across different subscription tiers. - [Billing of On-Cloud Recording and Recording Delivery](https://pre.trtc.io/document/45176.md): Tencent TRTC On-Cloud Recording is a cloud-based audio and video recording service that charges based on recording duration and video resolution. It is designed for developers using TRTC rooms to capture streams via recording robots. This overview explains the billing composition including subscription fees, usage calculation, pricing tiers for different video resolutions, and billing cycles. It also covers Web Page Recording and Recording Delivery components, providing a comprehensive understanding of TRTC recording service charges. - [Billing of MixTranscoding and Relay to CDN](https://pre.trtc.io/document/47631.md): MixTranscoding is a Tencent RTC paid service that mixes, transcodes, and repackages multiple audio and video streams within a TRTC room. This overview explains the daily pay-as-you-go billing model based on input duration, including audio and video transcoding fees calculated by resolution and codec. It also covers relay fees for streaming to third-party CDNs and details on usage calculation and billing cycles. - [Billing of Conversational AI Services](https://pre.trtc.io/document/67833.md): The Conversational AI service within Tencent RTC Engine provides real-time voice interaction between humans and large language models. This overview explains the billing components including audio call fees, Conversational AI service fees, and speech-to-text service fees. It targets developers and users integrating or utilizing Conversational AI, detailing free trial usage, monthly package options, and fee calculation methods. Integration guidance is also referenced for implementation. - [Billing of Speech AI Service](https://pre.trtc.io/document/67832.md): This document provides billing instructions for Tencent RTC's Speech-to-Text, AI Real-Time Translation, and Text-to-Speech services. These postpaid services offer 10,000 free minutes monthly and support multiple languages for real-time audio transcription, multilingual translation, and natural speech synthesis. The guide details pricing, metering, and usage policies to help users understand cost management across these AI recognition capabilities. - [Clould Slicing and Terminal Video Screenshot](https://pre.trtc.io/document/64803.md): Tencent Cloud Real-Time Communication (TRTC) offers Cloud Slicing and Terminal Video Screenshot SDKs designed for scenarios such as remote education, showroom streaming, and video conferencing. These features enable evidence collection, quality inspection, archiving, and replay by storing entire video call or live streaming processes. Cloud Slicing supports both audio slicing and video screenshot capabilities with billing based on usage duration, while Terminal Video Screenshot is available for Pro edition users with monthly billing. This overview explains pricing, billing formulas, usage statistics, and feature descriptions to help users understand and manage these services effectively. - [TRTC Overdue and Suspension Policy](https://pre.trtc.io/document/56211.md): Tencent Cloud Real-Time Communication (TRTC) Overdue and Suspension Policy outlines the rules for handling account arrears, service suspension, and resource management for TRTC products including Call, Conference, Live, and RTC-engine. It is designed for Tencent Cloud customers to understand billing cycles, suspension impacts, and recovery options to maintain uninterrupted real-time audio and video services. - [Chat Suspension Policy](https://pre.trtc.io/document/34352.md): Tencent Cloud Chat service suspension FAQ explains the policies and impacts of service suspension due to prepaid package expiration or account arrears. It guides users on how suspension affects Chat capabilities, resource retention and repossession timelines, and how to prevent suspension by monitoring account balance and renewing packages promptly. - [FAQs](https://pre.trtc.io/document/42737.md): Tencent Real-Time Communication (TRTC) FAQs provide answers on billing methods, usage statistics, discounts, and package details for audio and video communication services. This guide helps users understand how to view bills, estimate costs using the price calculator, and explains how usage durations and Monthly Active Users (MAU) are calculated across multiple subscription packages. - [TRTC Monthly Package Refund Instructions](https://pre.trtc.io/document/58588.md): Tencent RTC TRTC monthly package refund instructions provide a step-by-step guide on how users can request a refund within five days of purchase if the package remains unused. This guide explains the refund eligibility criteria, exceptions such as account suspension or usage of gifted call duration, and the procedure to submit a refund ticket via the Tencent Cloud Console. It ensures users understand the refund rules, including non-refundable discounts and the refund method. - [Chat Monthly Package Refund Instructions](https://pre.trtc.io/document/55095.md): Tencent Cloud Chat refund policy FAQ explains the conditions under which users can request refunds for Chat resource plans or feature packs. It covers the five-day unconditional refund period, usage restrictions, refund calculation methods, and scenarios where refunds are not supported. This guide helps users understand how to manage refunds effectively and the impact of returns on service availability.