Skip to content

Authentication

Capture pages behind login walls by providing credentials or agent instructions.

How it works

Many applications require authentication to access their pages. ScreenshotAgent’s AI agent can log in to your application before capturing screenshots. The agent maintains a persistent browser profile, so it only needs to log in once—subsequent captures reuse the authenticated session.

Configuration

Authentication can be configured at either the project level or the individual screenshot level:

  • Login URL — The URL of your login page. If omitted, the agent will auto-detect the login page if redirected.
  • Username / Email — The login identifier. Stored encrypted.
  • Password — The login password. Stored encrypted.

Note

Credentials are encrypted at rest. They are only decrypted when the capture agent needs to authenticate.

Complex authentication flows

For applications with multi-step sign-in (e.g., SSO with a password, or custom flows), use agent instructions to guide the capture agent:

Agent Instructions for SSO
Click the "Sign in with Google" button.
Enter the email address in the Google login form.
Enter the password and submit.
Wait for the redirect back to the application.

Note

A login that needs a fresh one-time code (2FA), a link from an email, or a captcha at every sign-in can't be automated. Use a test or demo account that signs in with a password.

Session persistence

ScreenshotAgent maintains browser profiles for each project. After the first successful login, the session cookies are preserved and restored for future captures. This means the agent does not need to log in every time, reducing capture time and avoiding rate limits on your login endpoint.