Remote integration

Maintainer reference.

The local HTTP remote service requires an access token. It is distinct from the website account API.

Its versioned routes include /api/v1/status, /api/v1/command and /api/v1/asset. Supported command payloads, authorization and status fields are defined in src-tauri/crates/api/src/http.rs and the associated API crate types for your installed version.

Use the connection details provided by Settings → Remote. Keep the token private and restrict access to a trusted local network. Integrations should handle unavailable connections and rejected commands without assuming content was sent live.

For operator setup, see Remote control.

For operating the app, see the Worship Studio guide.