Mux Live Streams API
A Live Stream represents a unique live stream of video being pushed to Mux. It includes configuration details (a Stream Key) for live broadcasting software/hardware and a Playback ID for playing the stream anywhere. Currently, RTMP is the only supported method of ingesting video. Use rtmp://global-live.mux.com:5222/app with the Live Stream's Stream Key for getting the video into Mux, and use https://stream.mux.com with the Live Stream's Playback ID for playback.A Live Stream can be used once for a specific event, or re-used forever. If you're building an application like Facebook Live or Twitch, you could create one Live Stream per user. This allows them to configure their broadcasting software once, and the Live Stream Playback ID will always show their latest stream.Each RTMP session creates a new video asset automatically. You can set up a webhook to be notified each time a broadcast (or Live Stream RTMP session) begins or ends with the video.live_stream.active and video.live_stream.idle events respectively. Assets that are created from a Live Stream have the same behavior as other Assets you create.Learn more about [how to go live in our guides](https://docs.mux.com/guides/start-live-streaming).
Mux Live Streams API is one of 38 APIs that Mux publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Live Streams. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 22 operations across 15 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against 4 base URLs: https://api.mux.com, https://image.mux.com, https://stream.mux.com, https://stats.mux.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Mux Live Streams API declares
3 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
It accepts HTTP basic authentication (accessToken).
It accepts HTTP bearer tokens (authorizationToken).
basicAuth— HTTP Basic auth using a Mux Access Token ID (username) and Secret (password).accessToken— The Mux Video API uses an Access Token and Secret Key for authentication. If you haven't already, [generate a new Access Token](https://dashboard.mux.com/setti…authorizationToken— OAuth authorization token, used as a Bearer Auth header
Paths & Operations 22
Across 15 paths, the API surfaces 22 operations — 4 DELETE, 6 GET, 1 PATCH, 5 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.
Create and manage live streams.
Schemas 29
The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are LiveStream (24 properties), CreateLiveStreamRequest (18 properties), AssetOptions (17 properties), InputSettings (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Mux 12
Other APIs Mux publishes across the network.
This is an independent, third-party profile of Mux Live Streams API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.