Browser sessions

When an agent runs browser automation, Flowra can keep a live browser session. The dashboard may show a side panel; the Browser API lets your app read status, embed the live view, send heartbeats, complete a browser-based connection, or close the session. For agent-facing tool slugs (Stagehand-style actions), see Native tools: Browser.

Session id

sessionId is the browser session id — often the chat thread id, or a standalone session id returned by the product when a browser run starts.

API endpoints

Method	Path	Purpose
`GET`	`/api/v1/browser/sessions/{sessionId}/status`	Alive flag, live pulse, `liveViewUrl` when available
`GET`	`/api/v1/browser/sessions/{sessionId}/view`	Live browser panel (iframe); requires auth
`POST`	`/api/v1/browser/sessions/{sessionId}/touch`	Heartbeat while the panel is open (including minimized)
`POST`	`/api/v1/browser/sessions/{sessionId}/complete-browser-connection`	After login in the live browser, save cookies/localStorage to a connected account
`POST`	`/api/v1/browser/sessions/{sessionId}/close`	Flush profile when possible, stop billing, end session

Example: status

curl -X GET "https://flowra.dev/api/v1/browser/sessions/YOUR_SESSION_ID/status" \
  -H "x-api-key: YOUR_API_KEY"

Example: close

curl -X POST "https://flowra.dev/api/v1/browser/sessions/YOUR_SESSION_ID/close" \
  -H "x-api-key: YOUR_API_KEY"

Full schemas: API reference — Browser.

Notes

touch keeps the live pulse fresh; it does not by itself extend Chromium idle lifetime — idle follows agent/user activity.
Treat live view URLs like sensitive capabilities if the session can access authenticated sites.

Getting started

Core building blocks

Data and runtime

Integrate and scale

Recipes

Native tools

Contributing

Browser sessions

Session id

API endpoints

Example: status

Example: close

Notes

​Session id

​API endpoints

​Example: status

​Example: close

​Notes

​Related

Session id

API endpoints

Example: status

Example: close

Notes

Related