Authenticated Pages

Extract data from websites that require login

Many websites gate their data behind authentication. Ev3ry handles this through saved logins — stored browser sessions that let the agent arrive on the page already authenticated.

Overview

The flow for authenticated extraction:

  1. Log into the target website in your own browser
  2. Export your session using the cookie-use extension
  3. Import the session into Ev3ry under the website's settings
  4. Run extractions — the agent loads your session before navigating

Step by step

1. Install cookie-use

cookie-use is a Chrome extension built by the Ev3ry team specifically for this workflow. It exports cookies, localStorage, and IndexedDB together as a single Playwright-compatible JSON file — no manual conversion needed.

Install it from the Chrome Web Store.

cookie-use captures everything in one click: cookies, localStorage, and IndexedDB. Other extensions typically only export cookies, which may not be enough for sites that store auth tokens in localStorage.

2. Log in to the target website

Open the website and complete the login process, including any two-factor authentication. Make sure you land on an authenticated page (not the login form).

3. Export your session

Click the cookie-use extension icon in your toolbar, then click Copy JSON or Download .json. The file contains your full session state for the current domain.

4. Import into Ev3ry

Go to your website's settings page in Ev3ry and find the Saved Login section. Drop the downloaded file or paste the copied JSON and save.

5. Run an extraction

Start a run normally. The agent will inject your session into the browser before navigating, so it arrives authenticated.

Tips

Export from an authenticated page. If you export from the login page or a public page, the session cookies may not include the auth token.

Check session lifetime. Some sites expire sessions after hours; others last weeks. If a run starts failing with authentication errors, the session has expired — re-export and reimport.

Test in incognito. Open the site in an incognito window. If you can access protected pages, your current session is still valid and doesn't need updating.

Prefer the local browser for sensitive accounts. Cloud browsers inject your cookies onto their servers. For high-value accounts, use the built-in browser so session data only leaves your machine as extracted output.

Known limitations

  • Two-factor authentication cannot be automated at login time. Complete 2FA once in your browser, then export the resulting session.
  • IP-bound sessions — some sites bind session tokens to the IP address that created them. Cloud browsers connect from different IPs and may trigger re-authentication. Use the local browser in this case.
  • CAPTCHAs on login pages cannot be solved automatically. Complete the login manually in your browser before exporting the session.
PreviousWhat is Ev3ry?NextExamples