Live streams

Create a stream, get an RTMP URL, push to it. When the broadcast ends the recording enters your library automatically.

Create a stream

curl -X POST https://api.streamos.in/api/public/v1/livestreams/ \
  -H 'Authorization: Bearer sk_live_…' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Weekly webinar",
    "customTags": {
      "course": "Physics 101",
      "batch": "JEE-2026"
    }
  }'

That is the whole response. A stream a second old has no duration, no recording and no start or end time, so those are not in it — read them from GET /livestreams/{public_id}/ once there is something to read.

Going live

Point any RTMP encoder at rtmp_url. The signature is already in the URL, so in OBS it goes in Server and Stream Key stays empty.

The broadcast is live as soon as the encoder connects. Viewers watch hls_url.

Scheduling for later

Books a slot without creating anything upstream. No RTMP URL and no stream key are issued — a push URL expires a few hours after it is minted, so one created a week ahead would be dead long before the broadcast.

The stream comes back with status: "SCHEDULED" and an empty rtmp_url. Start it on the day:

This is the call that reserves a channel and mints the push credentials. It takes no body, returns the same stream with READY_TO_STREAM and a real rtmp_url, and is safe to repeat — a stream that has already started is returned as-is rather than given a second channel.

Overriding DRM for one stream

drm_enabled (on both Create a stream and Scheduling for later) is a per-stream override of your organization’s own DRM default, applied to the recording — not the live broadcast, which goes out the same way either way. Omit it and the stream gets whatever your organization is set to. The one direction that is refused: sending truewhen your organization’s plan does not include DRM at all, which comes back DRM_NOT_AVAILABLE (409) rather than being created unprotected.

On a booking made with Scheduling for later, that choice is re-checked again when you actually call start— not just trusted from when you booked it. A stream booked with DRM on stays refused at start time if your organization’s plan no longer includes DRM by then; one booked with no override at all picks up whatever your organization’s default is on the day you start it, same as before this override existed.

curl -X POST https://api.streamos.in/api/public/v1/livestreams/ \
  -H 'Authorization: Bearer sk_live_…' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Weekly webinar",
    "drm_enabled": true
  }'

curl -X POST https://api.streamos.in/api/public/v1/livestreams/schedule/ \
  -H 'Authorization: Bearer sk_live_…' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Weekly webinar",
    "scheduled_at": "2026-09-25T10:00:00Z",
    "drm_enabled": true
  }'

When the stream ends

A stream ends on its own when the encoder stops pushing. You can also end it from your side:

This moves our record to ENDED and frees the concurrency slot. It does not stop a broadcast that is still being pushed — stop that in your encoder. Repeating the call is a no-op.

A stream nobody ever pushed to is closed automatically 24 hours after it was created, so an abandoned one does not hold a slot forever.

Two things then happen, minutes apart:

Encoding settings

drmis no longer part of these requests. Whether a recording is protected — along with its resolution ladder, subtitles and downloads — is a setting on your organization, configured once by the StreamOS team and used by every stream recording and every upload alike.

An organization with no encoding settings cannot start a stream — TRANSCODE_NOT_CONFIGURED (409), and nothing is created. Scheduling one is still allowed; the check happens when it is started, which is when the stream is actually created upstream.

Listing and fetching

curl https://api.streamos.in/api/public/v1/livestreams/htUTel8iPA6/ \
  -H 'Authorization: Bearer sk_live_…'

Where to find a stream’s id

Every stream endpoint takes the public_id — the short id the create call returned, like htUTel8iPA6. In the dashboard it is on Live, under the Live, Scheduled and Completed tabs — open a stream and copy the id from its page, or copy it straight from the ID column.

Status values

SCHEDULED → READY_TO_STREAM → ENDED. There is no LIVE status: nothing tells us when an encoder connects, so a stream in progress still reads READY_TO_STREAM.