Mux

Video infrastructure API for live streaming, on-demand video hosting, and analytics.

Detail	Value
Category	Media
Base URL	https://api.mux.com
Authentication	Basic Auth
Endpoints	6
Connector key	mux

Using Mux in a workflow

1. Go to Connections and click New Connection.
2. Pick Mux from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
POST /video/v1/assets	Create a video asset
GET /video/v1/assets	List video assets
GET /video/v1/assets/{ASSET_ID}	Get an asset
DELETE /video/v1/assets/{ASSET_ID}	Delete an asset
POST /video/v1/live-streams	Create a live stream
GET /video/v1/live-streams	List live streams

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /video/v1/assets

Create a video asset

Detail	Value
Operation ID	media.createAsset
Method	POST
Path	/video/v1/assets

Parameters

No parameters.

Request Body

Field	Type
input	array
playback_policy	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Mux connection from the Connection dropdown.
3. In the Operation dropdown, select media.createAsset.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mux API reference.

GET /video/v1/assets

List video assets

Detail	Value
Operation ID	media.listAssets
Method	GET
Path	/video/v1/assets

Parameters

Name	Location	Type	Required
limit	query	integer	No
page	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Mux connection from the Connection dropdown.
3. In the Operation dropdown, select media.listAssets.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mux API reference.

GET /video/v1/assets/{ASSET_ID}

Get an asset

Detail	Value
Operation ID	media.getAsset
Method	GET
Path	/video/v1/assets/{ASSET_ID}

Parameters

Name	Location	Type	Required
ASSET_ID	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Mux connection from the Connection dropdown.
3. In the Operation dropdown, select media.getAsset.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mux API reference.

DELETE /video/v1/assets/{ASSET_ID}

Delete an asset

Detail	Value
Operation ID	media.deleteAsset
Method	DELETE
Path	/video/v1/assets/{ASSET_ID}

Parameters

Name	Location	Type	Required
ASSET_ID	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Mux connection from the Connection dropdown.
3. In the Operation dropdown, select media.deleteAsset.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mux API reference.

POST /video/v1/live-streams

Create a live stream

Detail	Value
Operation ID	media.createLiveStream
Method	POST
Path	/video/v1/live-streams

Parameters

No parameters.

Request Body

Field	Type
playback_policy	array
new_asset_settings	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Mux connection from the Connection dropdown.
3. In the Operation dropdown, select media.createLiveStream.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mux API reference.

GET /video/v1/live-streams

List live streams

Detail	Value
Operation ID	media.listLiveStreams
Method	GET
Path	/video/v1/live-streams

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Mux connection from the Connection dropdown.
3. In the Operation dropdown, select media.listLiveStreams.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mux API reference.