Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Video
    • Overview
    • Control
    • Troubleshooting
  • Access management
  • Pricing policy
    • Authentication with the API
    • Getting started with the API
      • Overview
        • Overview
        • Get
        • List
        • BatchGet
        • Create
        • Update
        • Delete
        • BatchDelete
        • PerformAction
  • Audit Trails events
  • Release notes

In this article:

  • HTTP request
  • Path parameters
  • Response
  • Schedule
  1. API reference
  2. REST
  3. Stream
  4. Get

Video API, REST: Stream.Get

Written by
Yandex Cloud
Updated at April 24, 2025
  • HTTP request
  • Path parameters
  • Response
  • Schedule

Get the specific stream.

HTTP requestHTTP request

GET https://video.api.cloud.yandex.net/video/v1/streams/{streamId}

Path parametersPath parameters

Field

Description

streamId

string

Required field. ID of the stream.

ResponseResponse

HTTP Code: 200 - OK

{
  "id": "string",
  "channelId": "string",
  "lineId": "string",
  "title": "string",
  "description": "string",
  "thumbnailId": "string",
  "status": "string",
  "startTime": "string",
  "publishTime": "string",
  "finishTime": "string",
  "autoPublish": "boolean",
  // Includes only one of the fields `onDemand`, `schedule`
  "onDemand": "object",
  "schedule": {
    "startTime": "string",
    "finishTime": "string"
  },
  // end of the list of possible fields
  "createdAt": "string",
  "updatedAt": "string",
  "labels": "object"
}

Field

Description

id

string

ID of the stream.

channelId

string

ID of the channel where the stream was created.

lineId

string

ID of the line to which stream is linked.

title

string

Stream title.

description

string

Stream description.

thumbnailId

string

ID of the thumbnail.

status

enum (StreamStatus)

Stream status.

  • STREAM_STATUS_UNSPECIFIED: Stream status unspecified.
  • OFFLINE: Stream offline.
  • PREPARING: Preparing the infrastructure for receiving video signal.
  • READY: Everything is ready to launch stream.
  • ONAIR: Stream onair.
  • FINISHED: Stream finished.

startTime

string (date-time)

Stream start time.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

publishTime

string (date-time)

Stream publish time. Time when stream switched to ONAIR status.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

finishTime

string (date-time)

Stream finish time.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

autoPublish

boolean

Automatically publish stream when ready.
Switches status from READY to ONAIR.

onDemand

object

On-demand stream. Starts immediately when a signal appears.

Includes only one of the fields onDemand, schedule.

Stream type.

schedule

Schedule

Schedule stream. Starts or finished at the specified time.

Includes only one of the fields onDemand, schedule.

Stream type.

createdAt

string (date-time)

Time when stream was created.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

updatedAt

string (date-time)

Time of last stream update.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

labels

object (map<string, string>)

Custom labels as key:value pairs. Maximum 64 per resource.

ScheduleSchedule

Schedule stream type.
This type of streams start and finish automatically at the specified time.

Field

Description

startTime

string (date-time)

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

finishTime

string (date-time)

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

Was the article helpful?

Previous
Overview
Next
List
© 2025 Direct Cursus Technology L.L.C.