Create or reset template
This method creates or resets a flow configuration template.
Prototype
- Method:
PUT
- Endpoint:
https://api.agora.io/:region/v1/projects/:appId/rtls/ingress/stream-templates/:templateId
In the template, you can configure transcoding parameters for video or audio streams, as well as parameters for mitigating network latency.
Up to 10 flow configuration templates can be created under an app ID, each with a unique templatedId
. Specify the templateId
when creating a template; if a template corresponding to this ID already exists, the existing template will be reset with the incoming body data.
There are two ways to use flow configuration templates, which can be used in combination:
- Specify a global template for the app ID: All streaming keys under the app ID will use this template by default.
- Specify a configuration template for a specific streaming key: When using this key to push streams, the specific template will be used.
Request parameters
Authentication
-
HTTP Basic Authentication
Every time you send an HTTP request, you must pass in a credential in the
Authorization
field in the HTTP request header. See RESTful Authentication on how to generate it.Basic authentication is a simple authentication scheme built into the HTTP protocol. To use it, send your HTTP requests with an
Authorization
header that contains the word Basic followed by a space and a base64-encoded stringusername:password
.Example:
Authorization: Basic ZGVtbzpwQDU1dzByZA==
-
HTTP HMAC Authentication
Every time you send an HTTP request, you must pass in an API key in the
Authorization
field in the HTTP request header. See RESTful Authentication on how to generate it.Example:
Authorization: 123
Path parameters
Parameter | Data type | Required/Optional | Description |
---|---|---|---|
appId | String | Required | The app ID provided by Agora to each developer. After creating a project in Agora Console, you can get an app ID. The app ID is a unique identifier for a project. |
region | String | Required | Create an area for pushing the streaming key. Agora supports creation of stream keys by region. Currently, the following regions are supported:
Important Make sure that:
|
templateId | String | Required | The flow configuration template ID. The value can only include the following characters: a-z, A-Z, 0-9, and the length cannot exceed 12 bytes. The value of the flow configuration template ID can be set according to your business scenario. For example, "720p" and "1080p" for different target resolutions, or "gameA" and "gameB" for different game scenarios. |
Headers
Header | Data type | Description |
---|---|---|
X-Request-ID | String | The UUID (Universally Unique Identifier) of the request. After passing in this field, the Agora server will return this field in the response header. It is recommended to assign X-Request-ID a value. If no value is assigned, the Agora server will automatically generate a UUID and pass it in. |
Request body
The request body consists of a JSON Object type settings
and includes the following fields:
Parameter | Data type | Required/Optional | Description | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
transcoding | Object | Optional | Audio and video transcoding parameter configuration.
| ||||||||||||||||||||||||||||||||||||
jitterBuffer | Object | Optional | Network jitter buffer. Only takes effect when video transcoding is enabled.
|
Request example
Response parameters
Headers
Header | Data type | Description |
---|---|---|
X-Request-ID | String | The UUID (Universally Unique Identifier) of the request. The value is in its X-Request-ID header. If a request error occurs, print the value in the log to troubleshoot the problem. A 401 (Unauthorized) response status code means that there is no such field in the response header. |
Response body
For details about possible response status codes, see Response status codes.
If the status code is not 200
, the request fails. See the message
field in the response body for the reason for this failure.
If the status code is 200
, the request succeeds, and the response body includes the following parameters:
Parameter | Type | Description |
---|---|---|
status | String | The status of this request. success means the request succeeds. |
Response example
The following is a response example for a successful request:
To explore the RESTful API parameters, obtain sample code in various client languages, or test Media Gateway requests, refer to the Postman API reference.