API REFERENCE · LIVE STREAMING

SRT in & out

Planned (experimental): call our SRT listener with the source; we call your SRT destination with each language's dubbed feed.

01.When to use SRT

SRT is the broadcast-grade transport: packet recovery keeps the picture clean on lossy links, and the passphrase encrypts the link (AES) end to end. Protocols mix freely per session: SRT in with WHEP playback out, RTMP in with SRT pushes out (Create a session).

02.Ingest

Create the session with ingest.protocol: "srt"; the response carries ingest.srt_url + ingest.passphrase instead of the WHIP pair.

THE INGEST PAIR
{
  "ingest": {
    "protocol": "srt",
    "srt_url": "srt://ingest.thefamiliarlab.com:8890?streamid=live_77aq2c",
    "passphrase": "srt_pp_2c81ke…"
  }
}

Set both on any SRT encoder in caller mode (OBS, vMix, ffmpeg, hardware encoders); we listen. Send the camera feed and the full program audio, same as WHIP (What to send), and keep your encoder's default SRT latency, raising it for long-haul links.

03.Outputs

Each output created with protocol: "srt" names its destination: we will call your listener at srt_urlwith that language's dubbed feed once the session goes live -- a destination per language, no puller to run.

ON POST /v1/live/sessions
"outputs": [
  { "lang": "es", "protocol": "srt",
    "srt_url": "srt://ingest.yourplayout.com:9000?streamid=es-feed" },
  { "lang": "fr", "protocol": "srt",
    "srt_url": "srt://ingest.yourplayout.com:9000?streamid=fr-feed" }
]

04.Access

The API is enterprise-only: private access under a Studio contract, with volume pricing, raised limits, ProRes masters on request, and a named point of contact. Book a call and your key is issued with the contract.