Skip to main content
POST
Creates a live stream in the idle state and returns the broadcast credentials your encoder needs to start pushing video. Authenticated with your secret key. The response contains a single-use streamKey and an rtmpUrl that the broadcaster pastes into their encoder. Once the broadcaster connects, the stream automatically transitions to active and becomes visible in your feed. ShortKit supports two ingest and delivery protocols. Use protocol: "hls" (the default) for standard latency broadcasts, or protocol: "webrtc" for sub-second delivery to viewers — see Choosing a protocol.

Body parameters

string
Display title shown in the feed. Max 200 characters.
string
default:"hls"
Ingest and delivery protocol. One of hls or webrtc.
  • hls — Standard latency (a few seconds). Use with any RTMP-compatible broadcast software or hardware encoder.
  • webrtc — Sub-second latency. Viewers receive the stream in under a second end-to-end. The broadcast workflow is identical — your encoder still connects via the rtmpUrl returned in the response.
latencyMode and reconnectWindow apply only to hls streams and are ignored when protocol is webrtc.
string
default:"low"
HLS streams only. One of low, reduced, or standard. See Latency mode. Ignored when protocol is webrtc.
integer
default:"60"
HLS streams only. Seconds the stream will hold the slot if the broadcaster disconnects. Range 0–1800. Ignored when protocol is webrtc.
rtmpUrl and streamKey are sensitive credentials — anyone with them can broadcast under your stream. Forward them only to the broadcaster who will publish the stream. Do not log them, expose them to viewers, or commit them to source control.
The credentials are returned only on this Create response. If you lose them, delete the stream and create a new one.