Before You Start

Media Live is a broadcast-grade livestreaming service that supports features such as channel management and content encryption, making it an ideal option for media and broadcasting.

This document describes how to use application programming interfaces (APIs) to perform operations on Media Live, such as managing live transcoding templates and creating channels. For details about all supported operations, see API Overview.

Before calling a Media Live API, ensure that you are familiar with concepts related to Media Live. For details, see Media Live User Guide.

Media Live supports Representational State Transfer (REST) APIs, allowing you to call APIs using HTTPS. For details about API calling, see Calling APIs.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on regions. For the endpoints of Media Live, see Table 1. You can also query the endpoints of services on Regions and Endpoints.

**Table 1** Endpoints
Region	Detail	Endpoint
CN-Hong Kong	ap-southeast-1	live.ap-southeast-1.myhuaweicloud.com
AP-Singapore	ap-southeast-3	live.ap-southeast-3.myhuaweicloud.com

Constraints

Media Live sets a limit on the number of API calls to prevent service interruption caused by repeated API calls in a short period of time.

**Table 2** API request throttling
API Category	API Name	Max. User Requests	Max. API Requests
OTT Channel Management	Creating an OTT Channel Querying Channel Information Deleting Channel Information Modifying Channel Packaging Information Modifying Channel Input Information Modifying Channel Recording Information Modifying General Channel Information Changing the Channel Status Modifying Channel Transcoding Template Information Querying Channel Statistics	80 times/minute	80 times/minute
Integration with Cloud Eye	Querying Dimension Configurations Querying Instances	80 times/minute	80 times/minute
StreamConnect	Creating a Flow Querying Flows Deleting a Flow Obtaining Flow Details Starting a Flow Task Stopping a Flow Task Modifying a Flow Source Creating an Output of Pushing Streams to a Third Party Through SRT Updating an Output of Pushing Streams to a Third Party Through SRT Querying Outputs of Pushing Streams to a Third Party Through SRT Deleting an Output of Pushing Streams to a Third Party Through SRT	80 times/minute	80 times/minute

Concepts

Account
An account is created upon successful registration with the cloud platform. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. An account is a payment entity. Accounts should not be used directly to perform routine management. For security purposes, create IAM users and grant them permissions for routine management.
IAM user
An IAM user is created using an account to use cloud services. Each IAM user has its own identity credentials (password and access keys).

An IAM user can view the account ID and user ID on the My Credentials page of the console. The account, username, and password will be required for API authentication.
Region
A region is a physical location where cloud resources are deployed. Availability zones (AZs) in the same region can communicate with each other over an intranet, but AZs in different regions cannot. Deploying cloud resources in different regions can better suit certain user requirements or comply with local laws or regulations.
AZ
An AZ contains one or more physical data centers equipped with independent ventilation, fire, water, and electricity facilities. Compute, networking, storage, and other resources in an AZ are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to allow you to build cross-AZ, high-availability systems.
Project
Projects group and isolate resources (including compute, storage, and networking resources) across physical regions. A default project is provided for each region, and subprojects can be created under each default project. Users can be granted permissions to access all resources in a specific project. For more refined access control, create subprojects under a project and purchase resources in the subprojects. Users can then be assigned permissions to access only specific resources in the subprojects.

Figure 1 Project isolating model