Create a Mux live stream with RTMPS ingest and retrieve stream key
domain: docs.mux.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with your Mux Token ID and Token Secret using HTTP Basic Auth against the Mux Video API base URL.
POST to the live streams endpoint with a JSON body specifying playback_policy (e.g. 'public'), latency_mode, and any recording or reconnect_window settings.
From the response, extract stream_key and ingest rtmps URL (the ingest URL is a fixed rtmps endpoint; the stream key authorizes the session).
Configure your encoder (OBS, vMix, etc.) with the RTMPS ingest URL and stream key.
Poll GET on the live stream resource or use Mux webhooks to watch for status transitions (idle → active).
Construct a playback URL using the playback_id returned in the response to serve LL-HLS to viewers.
Known gotchas
A live stream is re-usable; each broadcast creates a new underlying asset. Do not delete and recreate the stream resource between broadcasts.
The stream key is equivalent to a secret credential; do not expose it to browser clients.
reconnect_window defaults to a short duration; increase it if your encoder may briefly disconnect.
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?