Live view

Base URL https://api.tilion.dev. The token-minting calls below need Authorization: Bearer $TILION_API_KEY; the streams authenticate with the minted view token instead. Every session can be watched live. Mint a view token, then open one of the streams below with it.

Mint a view token

POST /v1/session/{session_id}/view-token

{
  "token": "...",
  "expires_in": 300,
  "live_view_url": "https://api.tilion.dev/v1/session/.../live-view?token=..."
}

The token is short-lived and scoped to this one session, so it is safe to hand to a browser front end. The endpoint returns 404 if the desktop view is not enabled on this deployment, and 503 if live-view signing is not configured. For full_browser sessions there is a separate VNC token with the same shape:

POST /v1/session/{session_id}/vnc-token

Streams

Route	Auth	What it carries
`WS /v1/session/{id}/live?token=…`	view token	JPEG frames of the page. Works everywhere
`WS /v1/session/{id}/webrtc?token=…`	view token	A smoother video stream over WebRTC, where available
`WS /v1/session/{id}/vnc-ws?token=…`	VNC token	A VNC stream of a real desktop, for `full_browser` sessions
`GET /v1/session/{id}/live-view`	view token	A ready-made viewer page

/live-view is the fastest way to see a session: open the live_view_url from the token response in any browser. The WebSocket streams are for embedding the view in your own product.

Get started

MCP

Sessions

Fetch & jobs

Content

Agent & tasks

Live view & recordings

Account

Reference

Mint a view token

Streams

​Mint a view token

​Streams

Mint a view token

Streams