Mux Playback Restrictions API
Playback Restrictions allows you to set additional rules for playing videos. You can set the domains/hostnames allowed to play your videos. For instance, viewers can play videos embedded on the `https://example.com` website when you set the Playback Restrictions with `example.com` as an allowed domain. Any Video requests from other websites are denied. Additionally, you can set rules for what user agents to allow. Please see [Using User-Agent HTTP header for validation](https://docs.mux.com/guides/secure-video-playback#using-user-agent-http-header-for-validation) for more details on this feature.
Mux Playback Restrictions API is one of 38 APIs that Mux publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Playback Restrictions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 6 operations across 4 paths, and defines 10 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 2
Mux Playback Restrictions API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (accessToken).
It accepts HTTP bearer tokens (authorizationToken).
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 6
Across 4 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
Playback Restrictions allows you to set additional rules for playing videos. You can set the domains/hostnames allowed to play your videos. For instance, viewers can play videos e…
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are PlaybackRestriction (5 properties), UserAgentRestrictionRequest (2 properties), UserAgentRestrictionSettings (2 properties), ReferrerDomainRestrictionRequest (2 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 Playback Restrictions 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.