livekit
Pull media from a LiveKit room. The room and participant identity are determined by the access token you provide.
Example
Section titled “Example”curl -X POST "https://api.avflow.dev/v1/jobs" \ -H "Authorization: Bearer ${AVFLOW_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "name": "lk-ingest", "sources": [{ "name": "room_src", "type": "livekit", "config": { "serverUrl": "wss://your-project.livekit.cloud", "token": "<livekit-access-token>", "select": { "mediaType": "both" } } }], "nodes": [], "sinks": [{ "name": "rtmp_out", "type": "rtmp_push", "inputs": ["room_src"], "config": { "urls": ["rtmp://live.example.com/app/key"] } }] }'Generate tokens with the LiveKit server SDK.
Config
Section titled “Config”| Field | Type | Required | Description |
|---|---|---|---|
serverUrl | string | Yes | LiveKit server WebSocket URL (wss://…) |
token | string | Yes | JWT access token with subscribe grants |
select | SelectFilter | No | Filter participants or tracks |
Wiring
Section titled “Wiring”Multi-participant rooms usually need video_mixer and audio_mixer before RTMP or recording sinks.
Pricing
Section titled “Pricing”Billed as an RTC video source by resolution tier. Source pricing.