By default, /getPageSource returns HTML and nothing else - cookies set during the navigation are dropped after the response is sent. Set get_cookies=true to capture them.
Request
Response shape
When get_cookies=true, the response becomes JSON:
What you can do with the cookies
Replay them on your own client
If a site sets a session cookie that gates access to data, you can fetch the page through ScrapeUnblocker once, capture cookies, then make follow-up requests directly with those cookies attached. Faster than going through the proxy for every call.
This only works if the target site doesn’t bind sessions to the original IP. Many do. If r2 fails, route follow-up requests through ScrapeUnblocker too.
Debug bot-protection state
Some sites set bot-detection cookies (cf_clearance, __cf_bm, datadome, _dd_s) that are signed against the originating IP. Capturing them lets you confirm the protection actually completed - missing or empty bot cookies often correlate with a 403 on the next request.
Pin a proxy country for follow-up calls
The proxy field tells you which country pool served the request. If you need a follow-up call to land on the same continent (for IP-bound sessions), pass that value to proxy_country next time. See country targeting.
Combining with parsed_data
If you set both parsed_data=true and get_cookies=true, the response carries everything:
The html field is omitted in this case - you asked for parsed data, not raw HTML. 
