Find the exact module, copy the working request shape, and move from product workflow to API call without getting buried in the tree.
Write the workflow in plain language. We will turn it into a GPT-ready brief you can use to generate requests, module order, and starter payloads.
Multiview is the Engine module for building an operator monitoring wall from SRT, RTMP, or NDI inputs. The API stores the layout and input map, creates the conference-backed viewing surface, and keeps the runtime restreams aligned with the saved resource.
Multiview coordinates input restreams with a conference-backed viewing surface. The public endpoints are only valid for a resource whose visibility is PUBLIC.
POST /api/multiview/createChoose layout, visibility, inputs, and whether the runtime starts immediately.
POST /api/multiview/getByIdRead the saved input and conference bindings before sharing access.
POST /api/multiview/joinIssue a participant token for the authenticated operator workflow.
POST /api/multiview-public/getStatFor a public wall, read the runtime statistics associated with its input restreams.
Animated values illustrate request order; endpoint and payload contracts below are source-synced with Engine 8.7.
POST /api/multiview/create. Starting with inputs: [] is valid when you want to reserve the layout before attaching feeds.join endpoint to receive the conference room and participant token.getById and the input runtime statistics to confirm the saved state and media process agree.Public read, statistics, and join endpoints do not use x-access-token, but they return data only for a resource saved with visibility: PUBLIC. A public join may start the wall when its runtime is not ready. Treat the public id as shareable access material, apply rate limiting at the edge, and do not publish ids for private operations.
The Engine also contains an unauthenticated public-start route. It is intentionally not promoted here until its abuse-control policy is reviewed; use protected /api/multiview/start for operator automation.
Validation and lookup failures use the normal Engine error shape: { success: false, status, code, message, details }. Do not retry a validation failure until the required id, name, visibility, or participant fields are corrected.
Source binding: this page is reviewed against Engine 8.7@ef3dd337. Uncommitted phone-publish and AV mixer routes are not part of this public contract.
Create the saved wall and, when active is not false, prepare its conference/runtime. The authenticated user id is injected from the token; do not send user_id.
Next call: use getById to confirm normalized inputs, then join for an operator token.
A 400 response uses { success: false, status, code, message, details }.
Required operator-facing name, 1–120 characters.
Optional layout identifier. The Engine defaults to 4-tiles.
Optional overlay configuration stored with the wall.
Optional input definitions. Supported runtime source kinds include SRT, RTMP, and NDI variants; start with an empty array when you want to provision the wall before attaching feeds.
Optional PRIVATE or PUBLIC. The default is PRIVATE.
Optional initial runtime state. Defaults to active unless explicitly set to false.
Stable multiview identifier.
Operator-facing name.
Selected tile layout, for example 4-tiles.
Normalized video inputs and their runtime bindings.
PRIVATE or PUBLIC.
Conference backing the operator viewing surface.
Whether the multiview runtime should be active.