Skip to main content
GET
Returns the current status, startedAt, and (if applicable) endedAt for one or more live streams, addressed by playbackId. Authenticated with your publishable key — safe to call directly from a client app. Use this when you want to react to a stream’s state changing (for example, surfacing an “ended” UI when a broadcast finishes) without re-fetching the entire feed. The fields returned here are a subset of The Live Stream Object — only what’s useful for client-side state awareness. To inspect a stream’s full configuration (latency mode, reconnect window, etc.), use Get Live Stream with your secret key from your backend.

Query parameters

string
required
Comma-separated list of playback IDs to look up. Up to 50 per request.

Response shape

The response data is a map keyed by playbackId. Each entry contains:
string
Current lifecycle state. One of "idle", "active", or "ended".
string | null
ISO 8601 timestamp of when the broadcaster first connected. null while status is idle.
string
ISO 8601 timestamp of when the stream ended. Only present when status is "ended".
Playback IDs that don’t match a live stream owned by your organization are silently omitted from the response — there is no per-ID error. If data is empty, none of the requested IDs were valid.

When to use this vs. the feed

  • Feed (/v1/feed) — surface the live stream as part of normal content browsing. The feed response already includes liveStreamStatus on each item, so you don’t need a separate status call to render initial state.
  • This endpoint — keep a known set of streams (for example, those currently visible to a viewer in your UI) up-to-date as their state changes, without paying the cost of refetching the entire feed.

Errors