tencent cloud

Tencent Real-Time Communication

Release Notes and Announcements
Release Notes
Recent Product Announcement
TRTC Live (TUILiveKit) Product Launch Announcement
TRTC Conference Official Editions Launched
The commercial version of Conference is coming soon
Terms and Conditions Applicable to $9.9 Starter Package
Rules for the "First Subscription $100 Discount" Promotion
Announcement on the Start of Beta Testing for Multi-person Audio and Video Conference
TRTC Call Official Editions Launched
License Required for Video Playback in New Version of LiteAV SDK
TRTC to Offer Monthly Packages
Product Introduction
Overview
Concepts
Features
Strengths
Use Cases
Performance Statistics
Tencent RTC Quickplay: Experience Ultimate Real-Time Audio and Video Interaction!
Purchase Guide
Billing Overview
Free Minutes
Monthly subscription
Pay-as-you-go
TRTC Overdue and Suspension Policy
FAQs
Refund Instructions
User Tutorial
Free Demo
Call
Overview
Activate the Service
Run Demo
Integration
Offline Call Push
Conversational Chat
On-Cloud Recording
AI Noise Reduction
UI Customization
Calls integration to Chat
Additional Features
No UI Integration
Server APIs
Client APIs
Solution
ErrorCode
Release Notes
FAQs
Conference
Overview(TUIRoomKit)
Activate the Service (TUIRoomKit)
Run Demo(TUIRoomKit)
Integration(TUIRoomKit)
Screen Sharing (TUIRoomKit)
Schedule a meeting (TUIRoomKit)
In-meeting Call (TUIRoomKit)
UI Customization(TUIRoomKit)
Virtual Background (TUIRoomKit)
Conference Control (TUIRoomKit)
Cloud Recording (TUIRoomKit)
AI Noise Reduction (TUIRoomKit)
In-Conference Chat (TUIRoomKit)
Robot Streaming (TUIRoomKit)
Enhanced Features (TUIRoomKit)
Client APIs (TUIRoomKit)
Server APIs (TUIRoomKit)
FAQs (TUIRoomKit)
Error Code (TUIRoomKit)
SDK Update Log (TUIRoomKit)
Live
Billing of Video Live Component
Overview
Activating the Service (TUILiveKit)
Run Demo
No UI Integration
UI Customization
Live Broadcast Monitoring
Video Live Streaming
Voice Chat Room
Advanced Features
Client APIs
Server APIs
Error Codes
Release Notes
FAQs
RTC Engine
Activate Service
SDK Download
API Examples
Usage Guidelines
API Reference Manual
Advanced Features
AI Integration
Overview
Configure MCP Server
Install Skills
Integration Guide
FAQ
RTC RESTFUL API
History
Introduction
API Category
Room Management APIs
Stream mixing and relay APIs
On-cloud recording APIs
Data Monitoring APIs
Pull stream Relay Related interface
Web Record APIs
AI Service APIs
Cloud Slicing APIs
Cloud Moderation APIs
Making API Requests
Call Quality Monitoring APIs
Usage Statistics APIs
Data Types
Appendix
Error Codes
Console Guide
Application Management
Package Management
Usage Statistics
Monitoring Dashboard
Development Assistance
Solution
Real-Time Chorus
FAQs
Migration Guide
Billing
Features
UserSig
Firewall Restrictions
How to Downsize Installation Package
Android and iOS
Web
Flutter
Electron
TRTCCalling for Web
Audio and Video Quality
Others
Legacy Documentation
RTC RoomEngine SDK(Old)
Integrating TUIRoom (Web)
Integrating TUIRoom (Android)
Integrating TUIRoom (iOS)
Integrating TUIRoom (Flutter)
Integrating TUIRoom (Electron)
TUIRoom APIs
On-Cloud Recording and Playback (Old)
RTC Analytics Monthly Packages (Previous Version)
Protocols and Policies
Compliance
Security White Paper
Notes on Information Security
Service Level Agreement
Apple Privacy Policy: PrivacyInfo.xcprivacy
TRTC Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

Initiating a Call From the Server

PDF
Focus Mode
Font Size
Last updated: 2025-07-15 16:53:33

Effect Display

You can initiate a call and input uplink audio-video media streams through the server. The client-side effect of answering a call is as follows:
1V1 call
group call




Start Access

Initiating a Call From the Server

Example Request URL

https://console.tim.qq.com/v4/call_engine_http_srv/start_call_by_robot?sdkappid=88888888&identifier=administrator&
usersig=xxx&random=99999999&contenttype=json
Parameter
Description
Value
xxxxxx
SDKAppID resides in the country/region with a dedicated domain name
China: console.tim.qq.com, Singapore: adminapisgp.im.qcloud.com
https
request protocol
The request protocol is HTTPS, and the request method is POST.
console.tim.qq.com
Request domain
fixed as console.tim.qq.com
ver
protocol version number
fixed as v4
servicename
internal service name, different servicename corresponds to different service type
Example: v4/call_engine_http_srv/get_call_info, among them call_engine_http_srv is the servicename
command
Command word, combined with servicename to identify specific business functionality
Example: v4/call_engine_http_srv/get_call_info, among them get_call_info is the command
sdkappid
App ID obtained from the IM console
apply for access to obtain
identifier
userName must be an App administrator account for REST API calls
see App admin
usersig
password corresponding to the userName
refer to generate UserSig
random
Identify the random parameter of the current request
32-bit unsigned integer random number, value ranges from 0 to 4294967295
contenttype
Request format
The value is fixed as JSON.

Sample Request Packet

The following is a sample request packet for a video call from the server (userId: robot) to the client (userId: jack):
{
"Robot_Account":"robot", // robot userid, no heartbeat detection for robot
"CalleeList_Account":["jack"],
"Timeout":300000,
"UserData":"userdata-12345687",
"CallInfo":{
"MediaType": "Video",
"RoomId":"roomid-test",
"RoomIdType":2
},
"OfflinePushInfo": {
"PushFlag": 0,
"Title":"This is the push title",
"Desc": "This is offline push content"
"Ext": "{\\"entity\\":{\\"key1\\":\\"value1\\",\\"key2\\":\\"value2\\"}}"
}
}
Parameter
Description
Robot_Account
Robot ID
CalleeList_Account
Called member list
Timeout
Timeout time
CallInfo.MediaType
Call type. video call: "video". Voice call: "Audio".
CallInfo.RoomId
Room ID. Divided into Int and String two types.
CallInfo.RoomIdType
Room ID type. Int type: 1. String type: 2.
OfflinePushInfo
Offline push parameters. For details, see IM message format description

Sample Response Packet

{
"ErrorCode": 0,
"ErrorInfo": "",
"ActionStatus": "OK",
"RequestId": "Id-01f93f1a85c34d64a0e4cadb371deef8-O-Seq-997346",
"Response": {
"CallId": "35fd577d-1d10-4201-a40d-6d7316560986",
"CallResult": [
{
"Callee_Account": "jack",
"ResultCode": 0
}
]
}
}
Parameter
Description
ErrorCode
Error code. 0 indicates success, non-0 indicates failure
ErrorInfo
Error Message
ActionStatus
Request processing result. OK: processing successful; FAIL: processing failed.
RequestId
Unique request ID, returned for each request. RequestId is required for locating a problem.
Response
Call ID Call result

Input Media Stream on Server Side

TRTC server calls the stream push API to push online media streaming. See input media stream into room.
Note:
Input online media stream (StartStreamIngest) parameters for RoomIdType differ from those in server-initiated calls:
Note: Parameter interpretation for RoomIdType in server-initiated calls: 1 means Int type, 2 means String type.
Parameter interpretation for RoomIdType in input online media stream: 0 means Int type, 1 means String type.



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback