Mux · Arazzo Workflow

Mux Live Stream Lifecycle Control

Version 1.0.0

Create a live stream, disable it, re-enable it, and signal it complete to walk the operational lifecycle.

1 workflow 1 source API 1 provider
View Spec View on GitHub Video InfrastructureVideo StreamingLive StreamingVideo AnalyticsVideo AIEncodingArazzoWorkflows

Provider

mux-com

Workflows

live-stream-lifecycle
Create a live stream, then disable, enable, and signal complete.
Walks a live stream through disable, enable, and complete signals after creation to demonstrate operational control.
4 steps inputs: latencyMode outputs: liveStreamId, status
1
createLiveStream
Create a live stream with a public playback policy to operate on.
2
disableLiveStream
Disable the live stream so it will reject new RTMP connections.
3
enableLiveStream
Re-enable the live stream so it can accept connections again.
4
signalComplete
Signal that the live stream is finished to close out any active broadcast window after the configured reconnect period.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Mux Live Stream Lifecycle Control
  summary: Create a live stream, disable it, re-enable it, and signal it complete to walk the operational lifecycle.
  description: >-
    Exercises the operational controls that surround a Mux Video live stream
    without needing an active broadcast. The workflow creates a live stream,
    disables it so it rejects new connections, re-enables it, and finally signals
    that the live stream is complete to close out any active broadcast window.
    Every step spells out its request inline so the flow can be read and executed
    without opening the underlying OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-3740.20
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-3740.20
      capability_name: OTT & Streaming Delivery
      spec: mux-com-live-streams-api-openapi.yml
      confidence: 0.8
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: liveStreamsApi
  url: ../openapi/mux-com-live-streams-api-openapi.yml
  type: openapi
workflows:
- workflowId: live-stream-lifecycle
  summary: Create a live stream, then disable, enable, and signal complete.
  description: >-
    Walks a live stream through disable, enable, and complete signals after
    creation to demonstrate operational control.
  inputs:
    type: object
    properties:
      latencyMode:
        type: string
        description: Latency mode for the live stream (low, reduced, or standard).
        default: low
  steps:
  - stepId: createLiveStream
    description: >-
      Create a live stream with a public playback policy to operate on.
    operationId: create-live-stream
    requestBody:
      contentType: application/json
      payload:
        playback_policies:
        - public
        latency_mode: $inputs.latencyMode
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      liveStreamId: $response.body#/data/id
      status: $response.body#/data/status
  - stepId: disableLiveStream
    description: >-
      Disable the live stream so it will reject new RTMP connections.
    operationId: disable-live-stream
    parameters:
    - name: LIVE_STREAM_ID
      in: path
      value: $steps.createLiveStream.outputs.liveStreamId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      result: $response.body#/data
  - stepId: enableLiveStream
    description: >-
      Re-enable the live stream so it can accept connections again.
    operationId: enable-live-stream
    parameters:
    - name: LIVE_STREAM_ID
      in: path
      value: $steps.createLiveStream.outputs.liveStreamId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      result: $response.body#/data
  - stepId: signalComplete
    description: >-
      Signal that the live stream is finished to close out any active broadcast
      window after the configured reconnect period.
    operationId: signal-live-stream-complete
    parameters:
    - name: LIVE_STREAM_ID
      in: path
      value: $steps.createLiveStream.outputs.liveStreamId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      result: $response.body#/data
  outputs:
    liveStreamId: $steps.createLiveStream.outputs.liveStreamId
    status: $steps.createLiveStream.outputs.status

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/mux-com-live-stream-lifecycle-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.