All Products
Search
Document Center

ApsaraVideo Live:HotLiveRtcStream

Last Updated:Jan 14, 2026

Prefetches Real-Time Communication (RTC) streams.

Operation description

QPS limit

The queries per second (QPS) limit for a single user is 10 calls per second. API calls that exceed this limit are throttled, which may affect your business. Plan your calls accordingly.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

live:HotLiveRtcStream

none

*Domain

acs:live:*:{#accountId}:domain/{#DomainName}

None None

Request parameters

Parameter

Type

Required

Description

Example

RegionId

string

No

The region ID.

cn-shanghai

DomainName

string

Yes

The streaming domain.

example.com

AppName

string

Yes

The application name of the live stream to prefetch.

app

StreamName

string

Yes

The name of the live stream to prefetch.

stream

RegionCode

string

Yes

The prefetch area. For more information, see the RegionCode lookup table.

Note

For regions within China, specify the corresponding code from the "Region codes for China" table. For all other regions, specify the country code.

  • If the CodeRegionHasNoNode error is returned after you specify a RegionCode, the corresponding area is not covered by L1 nodes and cannot be prefetched. In this case, specify a different RegionCode.

ZHJ

AudioMsid

string

Yes

The audio Msid.

rts audio

VideoMsid

string

Yes

The video Msid.

rts video

ConnectionTimeout

string

No

The duration to maintain the prefetch connection. Unit: milliseconds. The default value, 0, means the connection is always maintained.

0

MediaTimeout

string

No

The custom timeout period for a timeout event. Unit: milliseconds.

100000

RegionCode lookup table

Region codes for China

NameCode
BeijingBEJ
TianjinTAJ
HebeiHEB
ShanxiSHX
Inner MongoliaNMG
LiaoningLIA
JilinJIL
HeilongjiangHLJ
ShanghaiSHH
JiangsuJSU
ZhejiangZHJ
AnhuiANH
FujianFUJ
JiangxiJXI
ShandongSHD
HenanHEN
HubeiHUB
HunanHUN
GuangdongGUD
GuangxiGXI
HainanHAI
ChongqingCHQ
SichuanSCH
GuizhouGUI
YunnanYUN
TibetTIB
ShaanxiSHA
GansuGAN
QinghaiQIH
NingxiaNXA
XinjiangXIN
TaiwanTAI
Hong KongHKG
MacaoMAC

Country codes

NameCode
Papua New GuineaPG
SlovakiaSK
PeruPE
LatviaLV
United Arab EmiratesAE
CanadaCA
CubaCU
MauritaniaMR
JapanJP
ArmeniaAM
TurkmenistanTM
RussiaRU
BelarusBY
GuineaGN
IraqIQ
ArgentinaAR
ChileCL
EswatiniSZ
Congo (DRC)CD
BelgiumBE
KazakhstanKZ
SerbiaRS
TürkiyeTR
NamibiaNA
LithuaniaLT
Puerto RicoPR
Congo (Brazzaville)CG
New CaledoniaNC
MoroccoMA
GreenlandGL
KuwaitKW
LiberiaLR
UkraineUA
IndonesiaID
MyanmarMM
BoliviaBO
MoldovaMD
GreeceGR
New ZealandNZ
Solomon IslandsSB
EthiopiaET
FijiFJ
YemenYE
CyprusCY
Bosnia and HerzegovinaBA
EritreaER
GermanyDE
PakistanPK
Central African RepublicCF
CroatiaHR
EgyptEG
ThailandTH
Costa RicaCR
TanzaniaTZ
LaosLA
LibyaLY
TunisiaTN
PolandPL
United KingdomGB
Equatorial GuineaGQ
ChinaCN
IcelandIS
OmanOM
MongoliaMN
ChadTD
United StatesUS
MexicoMX
KyrgyzstanKG
SurinameSR
IndiaIN
Guinea-BissauGW
VenezuelaVE
ItalyIT
AlgeriaDZ
QatarQA
FranceFR
South AfricaZA
NorwayNO
PortugalPT
HungaryHU
South KoreaKR
UzbekistanUZ
BurundiBI
EstoniaEE
BangladeshBD
BhutanBT
AfghanistanAF
SwitzerlandCH
BelizeBZ
Timor-LesteTL
HaitiHT
TogoTG
AlbaniaAL
CameroonCM
NicaraguaNI
NigeriaNG
HondurasHN
Burkina FasoBF
MozambiqueMZ
GeorgiaGE
VanuatuVU
ParaguayPY
LuxembourgLU
LebanonLB
UgandaUG
MaliML
Saudi ArabiaSA
PalestinePS
MontenegroME
ColombiaCO
PhilippinesPH
SwedenSE
FinlandFI
KenyaKE
RomaniaRO
PanamaPA
JordanJO
RwandaRW
LesothoLS
North MacedoniaMK
ZambiaZM
SyriaSY
SpainES
EcuadorEC
GabonGA
IrelandIE
Dominican RepublicDO
GhanaGH
MadagascarMG
MalaysiaMY
AustriaAT
TajikistanTJ
DenmarkDK
UruguayUY
CambodiaKH
SenegalSN
El SalvadorSV
Sierra LeoneSL
Brunei DarussalamBN
Western SaharaEH
NigerNE
IranIR
GuyanaGY
AngolaAO
BotswanaBW
BrazilBR
AustraliaAU
Côte d'IvoireCI
Czech RepublicCZ
GambiaGM
BeninBJ
VietnamVN
SudanSD
NetherlandsNL
DjiboutiDJ
SloveniaSI
NepalNP
ZimbabweZW
JamaicaJM
MalawiMW
AzerbaijanAZ
SomaliaSO
IsraelIL
Falkland Islands (Malvinas)FK
North KoreaKP
GuatemalaGT
BahamasBS
Sri LankaLK
SingaporeSG
BahrainBH

Response elements

Element

Type

Description

Example

object

The ID of the request.

RequestId

string

The request ID.

16BFE188-B193-4C3C-ADC5-79A7E31486EA

Examples

Success response

JSON format

{
  "RequestId": "16BFE188-B193-4C3C-ADC5-79A7E31486EA"
}

Error codes

HTTP status code

Error code

Error message

Description

400 InvalidParam Parameter invalid. Illegal input parameters
400 NoSpecialConfiguration no special configuration for domain name.
400 CodeRegionHasNoNode this region has no corresponding node.
500 InternalError The request processing has failed due to backend service exception.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.