Vindral Live

The Vindral Live tab stores the API credentials Composer uses to talk to Vindral Live, RealSprint's cloud streaming platform. The credentials are read by Composer's Script Engine helper CallVindralApiAsync(), which lets a project script invoke arbitrary Vindral Live REST endpoints (channel listing, stream-target management, etc.) without the project author hard-coding URLs or keys into the script.

Settings window — Vindral Live tab

Configure the Vindral Live API connection settings for streaming integration.

Credentials

  • API Base URL (VindralLiveApiBaseUrl) — base URL of the Vindral Live REST API. Endpoint paths supplied to CallVindralApiAsync() are appended to this value, so include the trailing slash. Default: https://api.cdn.vindral.com/v1/. Override only when pointing Composer at a staging or on-prem Vindral Live deployment.
  • API Key (VindralLiveApiKey) — the bearer key used to authenticate against the Vindral Live REST API. Issued by RealSprint per customer / account. Treat as a secret — the key is persisted encrypted under EncryptionKey (see General → Workstation security) so wiping or rotating that key invalidates this one too.

When the credentials are used

CallVindralApiAsync() requires both fields to be non-empty; if either is blank, the call fails with an error in the log identifying which field is missing. There is currently no input or target component that uses these credentials — they're a Script Engine convenience for projects that need to coordinate with Vindral Live. See the Script Engine → Asynchronous HTTP calls page for the helper's full signature and response shape.