Accept a WHIP publish into LiveKit via Ingress and forward it to room participants

domain: docs.livekit.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create an Ingress with CreateIngress via the LiveKit Server API/CLI, setting input_type to WHIP_INPUT
  2. Read the returned IngressInfo.url (WHIP base URL) and stream_key from the response
  3. Configure the encoder/browser publisher to POST its SDP offer to url + "/" + stream_key (e.g. http://host:8080/w/<streamKey>)
  4. Send the stream key as a bearer token in the WHIP POST's Authorization: Bearer <streamKey> header (the server also tolerates a missing "Bearer " prefix from some encoders)
  5. Set enable_transcoding explicitly if you need codec normalization — unlike RTMP ingress, WHIP ingress does not transcode by default

Known gotchas

Related routes

Configure LiveKit Ingress to accept an RTMP stream from OBS and distribute it to WebRTC participants
docs.livekit.io · 6 steps · unrated
Publish a WebRTC stream to Cloudflare Stream Live via WHIP and play it back via WHEP
developers.cloudflare.com · 6 steps · unrated
Ingest a WebRTC stream into Mux via WHIP
docs.mux.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans