Pass your session cookies
- Sign in to the site in Chrome, Edge or Firefox.
- Open DevTools (
F12), go to Application (Chrome, Edge) or Storage (Firefox), then Cookies, and pick the site. - Copy the cookies: either the ones that look like a session (
session,auth,token,sid), or select every row and copy them all. - Send them in
cookies:
cookies takes the usual name=value; name=value form, or the rows exactly as you copied them from Chrome’s cookie table (tab-separated). Spidra reads the name, value, domain and path from each row and ignores the other columns.
The same field works on Batch scrape, Crawl and Map. In the dashboard, it’s Authentication on the Scrape form and the Login tab under More settings on Crawl.
Log in with browser actions
For a plain login form, type the details and submit before the page is read:waitFor on the Logout link confirms the login worked; if it didn’t, the job fails at that step and costs nothing. What you type is never sent to the AI and is masked in your logs. Logins with a CAPTCHA, a one-time code or single sign-on usually need cookies instead.
Good to know
- Cookies are never stored. They’re used for the job and dropped. That’s also why a batch retry needs them sent again.
- Sessions expire. If pages start coming back logged out, copy fresh cookies.
- Copy from the right domain. Cookies belong to one site; copy them from the domain you’re scraping.
- Use your own accounts. You’re responsible for following each site’s terms and the law, including for content behind a login.

