Skip to main content
GET
Get a live browser URL
Request the live-view URL using your API key and an existing run ID:
The response is { "url": "wss://…" }. Connect to that URL exactly as returned; it includes the authorization needed for the live view. Treat it as a credential-bearing URL and keep it out of public logs.

Frames

Where live capture is available, JSON messages with type: "frame" contain: Filter for type: "frame" before reading those fields. For a preview image, use data:image/jpeg;base64, followed by b64 as the image source. Frames are a live visual feed, not a durable recording, task-control channel, or completion signal. Some execution paths do not produce live frames. Use SSE or polling for authoritative task state and includeEvents=true for available screenshot history. 404 can mean the run is inaccessible or live streaming is unavailable. A returned URL does not guarantee that a frame will arrive. Current SDKs and MCP tools do not have a wrapper for this endpoint.

Authorizations

Authorization
string
header
required

Use a pre.dev API key from https://pre.dev/projects/key.

Path Parameters

id
string
required

24-character record ID.

Pattern: ^[a-fA-F0-9]{24}$

Response

Connect to the returned WebSocket URL.

url
string<uri>
required

Credential-bearing WebSocket URL. Keep private and use only for the requested batch.