Mux Direct Uploads API
Direct upload allows you to push assets directly to Mux storage instead of needing to go through your own first. When you create a new direct upload, we'll give you back a signed URL for a Google Cloud Storage bucket. Their storage API is S3 compatible, so whatever tool you use to upload to either GCS or S3 should work, just remember you're probably uploading large video files and should [take advantage of things like resumable or multipart uploads](https://cloud.google.com/storage/docs/json_api/v1/how-tos/resumable-upload).Particularly for customers that deal with a lot of user-generated content, it's common to expect quite a few abandoned uploads. To keep those abandoned uploads from cluttering up your asset lists, we don't create an asset for you until the upload is complete. Once that asset is created, you can expect all of the normal asset-related webhooks.
Mux Direct Uploads API is one of 38 APIs that Mux publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Direct Uploads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 4 operations across 3 paths, and defines 11 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 Direct Uploads 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 4
Across 3 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Create direct upload URLs and inspect upload status.
Schemas 11
The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are AssetOptions (17 properties), InputSettings (11 properties), Upload (9 properties), CreateUploadRequest (4 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 Direct Uploads 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.