Custom Cookies

Add your own cookies to BrowserAPI and receive customised responses.

Custom cookies are an extremely powerful feature of BrowserAPI. For example, they can be successfully used to scrape content as authenticated users of the targeted website.

Custom Cookies without JavaScript Rendering

When you are not using JavaScript rendering, custom cookies should be added in the WSA-Cookie custom header. Simply pass the name and value of the cookie(s) to this header when you send your request.

Integration Examples

curl --request GET --url "<YOUR_API_KEY>&" --header "Wsa-Accept: application/json" --header "WSA-Cookie: name1=value1; name2=value2"
Response Example
    "cookies": {
        "name1": "value1",
        "name2": "value2"

Custom Cookies with JavaScript Rendering

When using JavaScript rendering, custom cookies should be passed in a list in the cookies parameter. Each cookie object will have 3 properties: name, value and domain. Here is an example:

[{"name":"cookie_name1", "value":"cookie_value1", "domain":"cookie_domain1"},{"name":"cookie_name2", "value":"cookie_value2", "domain":"cookie_domain2"},{"name":"cookie_name3", "value":"cookie_value3", "domain":"cookie_domain3"}]

And this is the URL encoded value from the example above:


Warning! Please make sure that you passed the correct domain value in the cookie objects. We used "domain":"" in the examples below because we want those cookies to be set on the domain.

Integration Examples

curl --request GET --url "<YOUR_API_KEY>&render_js=1&"
Response Example

	<meta name="color-scheme" content="light dark">

	<pre style="word-wrap: break-word; white-space: pre-wrap;">{
  "cookies": {
    "cookie_name1": "cookie_value1", 
    "cookie_name2": "cookie_value2", 
    "cookie_name3": "cookie_value3"


Important! The url parameter has to be encoded.

( i.e. & )

Last updated