Skip to main content

Changelog · October 31, 2026

Read pages behind a login

Your dashboard, as its user sees it.

By · Last updated: October 2026

TL;DR

Sign in to a site once in a browser, save its state — the cookies and localStorage, in the storageState format Playwright writes — and upload it with POST /auth_profiles. Then send auth_profile with any request but /lighthouse, /scrape included, and the page is loaded as that signed-in visitor: the account page, the dashboard, the admin screen. Nothing logs in again, so there is no password to hand over and no login flow to script. What the site renews during each visit is kept, so a session the site keeps rolling stays alive while you use it. It costs nothing extra.

Free plan, no credit card. 1,000 credits a month.

The state is encrypted at rest and never returned by the API, and a profile is used only on the domains it names. Its results are stored apart and served only to requests made with it. Every visit goes out from the one exit the session is used from, because sites end a session that moves. When a site answers with its sign-in form instead of the page, the request fails without charge and the profile's signed_out_at says when: sign in again and upload the new state. The MCP server's tools take auth_profile too.

Sign in once, save the state
npx playwright codegen --save-storage=state.json https://shop.example.com/login
Read a page as that visitor
curl -X POST https://urlpipe.dev/markdown \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://shop.example.com/account/orders", "auth_profile": "ap_7Qm2sX9kLw4RtB1nYc8vDf3H", "sync": true}'

Endpoints

The endpoints on this page

FAQ

Frequently asked questions

No, and it never sees your password. You sign in once in your own browser; URLpipe reuses the session that sign-in left behind.

Try it on the free plan.

Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.