Use the headers parameter to send custom HTTP headers and cookies with your request. This is useful when the target website requires specific headers (like User-Agent, Referer, or Cookie) to return the expected content.
Invalid or mismatched headers may cause the request to be blocked
If you override critical headers (e.g. Accept-Encoding), it may impact response parsing
Set a User-Agent to request the desktop or mobile version of a page
Force a language or locale-specific version of a page (e.g. Accept-Language: fr-FR)
Pre-set a consent Cookie so cookie-banner or region interstitials don’t block the page content
Keep a consistent Cookie-based session across multiple requests, e.g. to preserve a currency, search filters, or cart state you set on an earlier request
Pass an Authorization header or API key required by an endpoint you have your own legitimate credentials for, such as your own site, a sandbox environment, or a partner API