Create channel

Available in Classic and VPC

Create a live channel for streaming.

Request

This section describes the request format. The method and URI are as follows:

Request headers

For information about the headers common to all Live Station APIs, see Live Station request headers.

Request body

You can include the following data in the body of your request:

Request example

The request example is as follows:

curl --location --request POST 'https://livestation.apigw.ntruss.com/api/v2/channels' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'x-ncp-region_code: KR' \
--header 'Content-Type: application/json' \
--data '{
    "channelName": "testchannel",
    "envType": "DEV",
    "outputProtocol": "LL_HLS",
    "cdn": {
        "createCdn": true,
        "cdnType": "GLOBAL_EDGE",
        "profileId": 4207,
        "regionType": "KOREA"
    },
    "qualitySetId": 2585,
    "useDvr": true,
    "immediateOnAir": true,
    "timemachineMin": 360,
    "record": {
        "format": "MP4",
        "type": "AUTO_UPLOAD",
        "bucketName": "mybucket",
        "filePath": "/livestation",
        "accessControl": "PRIVATE"
    },
    "isStreamFailOver": true,
    "drmEnabledYn": false
}'

Response

This section describes the response format.

Response body

The response body includes the following data:

Response status codes

For information about the HTTP status codes common to all Live Station APIs, see Live Station response status codes.

Response example

The response example is as follows:

{
    "content": {
        "channelName": "testchannel",
        "cdn": {
            "createCdn": true,
            "cdnType": "GLOBAL_EDGE",
            "cdnInstanceNo": 1***2,
            "profileId": 4207,
            "regionType": "KOREA"
        },
        "qualitySetId": 2585,
        "useDvr": true,
        "immediateOnAir": true,
        "timemachineMin": 360,
        "channelId": "ls-20250818******-UbUBe",
        "uploadPath": "/mybucket/livestation",
        "envType": "DEV",
        "record": {
            "type": "AUTO_UPLOAD",
            "bucketName": "mybucket",
            "filePath": "/livestation",
            "format": "MP4",
            "accessControl": "PRIVATE"
        },
        "outputProtocol": "LL_HLS",
        "origin": {
            "originDomain": "*****.video.media.ntruss.com",
            "originPath": "27***85"
        },
        "isStreamFailOver": true,
        "drmEnabledYn": false
    }
}

Set streaming video security

Various settings are available to secure video content for streaming on the channel you create.

Content access control

By integrating with the Global Edge service, you can restrict access to streaming video content through Global Edge's content authentication control. Content authentication control methods include Signed URL and JSON Web Token. See Signed URL and JSON Web Token in the Global Edge user guide for how to use each method.

• When issuing an authentication token, you must enter the wildcard path under ACL for Signed URL and path for JSON Web Token respectively.
  • Wildcard path: /live/video/{channelId}/*
• You must set Edge Auth to the output protocol of the channel that created Edge Auth in the cache settings of Global Edge. For more information, see the Global Edge API guide.
  • Extensions excluded from authentication
    • HLS: .ts, .jpg
    • HLS/DASH: .ts, .jpg, .m4s, .m4v, .m4a
    • LL_HLS: .jpg, .m4s, .m4v, .m4a
  • Extension that forwards the authentication token to the source
    • HLS: .m3u8
    • HLS/DASH: .m3u8, .mpd
    • LL_HLS: playlist.m3u8

Content protection

By integrating with the One Click Multi DRM service, you can encrypt and stream video content through multi DRM to prevent piracy and distribution. You can easily set DRM features through the drm object when creating a channel, and multi DRM is applied according to the selected output protocol. For more information on encryption methods by DRM technology, supported devices, platforms, and versions, etc., see the DoveRunner (formerly PallyCon) guide.