Use case
Scrape what sits behind a login, and keep the login working.
The data worth having is rarely on a public page. A Scrappy session signs in once, saves that sign-in as a profile, and starts every later session already signed in — from the same IP, so the site sees a returning visitor.
Last updated
Sign in once
Start a session, sign in yourself in the live viewer (or let your code do it), then capture the session as a saved login. Two-factor prompts and security questions are answered by a person in the viewer, from a laptop or a phone.
Replay from the same place
Each saved login keeps its own residential exit IP. Replaying a session cookie from a new address on every run is one of the clearest signs of automation; replaying it from the same address is what a person's laptop looks like.
Know when it stops working
Sites end sessions. When a saved login lands on a sign-in page instead of the app, Scrappy refuses to overwrite the stored login with a signed-out one and sends a webhook, so you re-authenticate once rather than discovering a week of empty results.
Questions
- Is this allowed?
- Automating your own accounts, or accounts you are authorised to use, is generally a matter of each site's terms. Read them; Scrappy does not decide that for you.
- Can I try it before paying?
- Yes. A new account gets 100 credits, enough for a few sessions of real use. A session costs 5 credits to start and 1 per minute after that.
Start
Try it on the site you need this week. The first 100 credits are free.
Enough for ten scrapes or a first hour in the cloud browser. No card, no call, no minimum.