Dolby.io · Arazzo Workflow

Dolby OptiView Inspect an Engine's Last Run

Version 1.0.0

Pick an engine on a channel, fetch its most recent run, then list its full run history.

1 workflow 1 source API 1 provider
View Spec View on GitHub MediaStreamingReal-Time StreamingWebRTCLive StreamingLow LatencyVideoAudioBroadcastPlayerAdvertisingDolby OptiViewMillicastTHEOliveTHEOplayerArazzoWorkflows

Provider

dolby-io

Workflows

inspect-engine-last-run
Resolve an engine, read its last run, and list all of its runs.
Lists a channel's engines, then reads the last run and the full run history of the first engine.
3 steps inputs: authorization, channelId outputs: engineId, lastRunStart, runs
1
listEngines
get-channel-engines
List the channel's engines and capture the id of the first engine.
2
getLastRun
get-engine-last-run
Fetch the engine's most recent run. The run object includes engineId, start, config, and startType under data.
3
listRuns
get-engine-runs
List the full run history for the engine.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Dolby OptiView Inspect an Engine's Last Run
  summary: Pick an engine on a channel, fetch its most recent run, then list its full run history.
  description: >-
    Drills into the run history of a single transcoding engine. The workflow
    lists the engines on a channel, selects the first one, fetches that engine's
    most recent run (start, stop, and configuration), and then lists the engine's
    complete run history. The three read operations chain on the engine id so a
    single pass yields both the latest run and the full timeline. Every step
    inlines its Authorization header so the flow can be read and executed without
    opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: theoliveApi
  url: ../openapi/dolby-io-theolive-api-openapi.yml
  type: openapi
workflows:
- workflowId: inspect-engine-last-run
  summary: Resolve an engine, read its last run, and list all of its runs.
  description: >-
    Lists a channel's engines, then reads the last run and the full run history
    of the first engine.
  inputs:
    type: object
    required:
    - authorization
    - channelId
    properties:
      authorization:
        type: string
        description: HTTP Basic Authorization header value.
      channelId:
        type: string
        description: The id of the channel whose engine should be inspected.
  steps:
  - stepId: listEngines
    description: List the channel's engines and capture the id of the first engine.
    operationId: get-channel-engines
    parameters:
    - name: id
      in: path
      value: $inputs.channelId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      engineId: $response.body#/data/0/id
  - stepId: getLastRun
    description: >-
      Fetch the engine's most recent run. The run object includes engineId,
      start, config, and startType under data.
    operationId: get-engine-last-run
    parameters:
    - name: id
      in: path
      value: $steps.listEngines.outputs.engineId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      lastRunStart: $response.body#/data/start
      lastRunEngineId: $response.body#/data/engineId
  - stepId: listRuns
    description: List the full run history for the engine.
    operationId: get-engine-runs
    parameters:
    - name: id
      in: path
      value: $steps.listEngines.outputs.engineId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      runs: $response.body#/data
  outputs:
    engineId: $steps.listEngines.outputs.engineId
    lastRunStart: $steps.getLastRun.outputs.lastRunStart
    runs: $steps.listRuns.outputs.runs

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/dolby-io-inspect-engine-last-run-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 email required.

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