Cookie parser
Paste Set-Cookie lines from a response, or a Cookie header from your browser: each cookie is listed with its value and attributes, and the cookies are joined into the one Cookie header a scraping request sends.
The Cookie header to send: Cookie: session_id=8f2c1a9d; region=us-east; consent=accepted
| Cookie | Value | Attributes |
|---|---|---|
| session_id | 8f2c1a9d | Path=/; HttpOnly; Secure |
| region | us-east | Max-Age=86400; SameSite=Lax |
| consent | accepted | Path=/; Max-Age=31536000 |
Worked out in your browser. Nothing you paste is stored, sent or added to the page address, so tokens and cookies stay on your machine.
What it is for when you scrape
Some pages answer differently with a cookie: a consent choice that removes a banner, a region or currency setting, a session that a site expects to see before it shows prices. Many scraping APIs let you pass cookies with the request, usually as a header option or a cookies parameter; check the API's documentation for the name it uses.
Send only the name=value pairs: attributes such as Path, Max-Age and HttpOnly tell a browser how to store a cookie and are not sent back. Cookies from a logged-in session belong to an account, and scraping behind a login is something many APIs do not support and many sites' terms forbid.