capabilities.work

Persistent Profile Session

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

Recipe · 4 steps

Persistent Profile Session

with Hyperbrowser

Create a persistent profile and run a session that saves state back to it.

  1. Create a persistent browser profile that will retain cookies, storage, and authenticated state across sessions.
  2. Launch a cloud browser session bound to the new profile with change persistence enabled so state captured during the session is saved back.
  3. Read the session back to confirm it launched against the profile and is in the active status before any authentication is performed.
  4. Stop the session, which persists the captured cookies and storage back into the profile for reuse in future sessions.
What you'll need to have ready
  • apiKey: Hyperbrowser account API key sent in the x-api-key header.
  • profileName: A human-readable name for the new persistent profile.
For your developer

Arazzo workflow hyperbrowser:persistent-profile-session, 4 operations: post-api-profile → 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 RunSession LifecycleSession Recording RetrievalWeb Crawl and RetrieveWeb Search then Fetch