Skip to main content

Managing Sessions

Sessions keep a single browser context alive while you iterate on commands or scrape content. You can let the backend create one on demand or manage it explicitly.

List sessions​

curl "http://localhost:8082/browser/sessions"

Create a session​

curl -X POST "http://localhost:8082/browser/sessions"

Delete a session​

curl -X DELETE "http://localhost:8082/browser/sessions/session-123"

Use the same session_id in commands, content fetches, and streams to keep state (cookies, viewport, navigation history) intact between calls.