capabilities.work

Session Lifecycle

A 3-step recipe with Hyperbrowser. We can help you get access.

Recipe · 3 steps

Session Lifecycle

with Hyperbrowser

Create, inspect, and stop a single cloud browser session.

  1. Create a new cloud browser session using the supplied launch options and capture its id and connection endpoints.
  2. Read the session back by id to confirm it launched and is in the active status before any automation is driven against it.
  3. Stop the session to release the cloud browser and end billing once the automation work against it is complete.
What you'll need to have ready
  • apiKey: Hyperbrowser account API key sent in the x-api-key header.
  • useStealth: Whether to launch the session with stealth mode enabled.
  • useProxy: Whether to route the session through a managed proxy.
  • timeoutMinutes: Idle timeout in minutes before the session is auto-stopped.
For your developer

Arazzo workflow hyperbrowser:session-lifecycle, 3 operations: post-api-session → get-api-session-id → put-api-session-id-stop. Specs on APIs.io.

More recipes with Hyperbrowser

Browser Use Task RunCrawl Site and RetrieveExtract Structured DataHyperAgent Task RunPersistent Profile SessionSession Recording RetrievalWeb Crawl and RetrieveWeb Search then Fetch