Parameters
All Scraper APIs support the parameters listed in this page. Note that each individual target may have custom parameters.
Parameter | Header name | Default value | Description | Example |
---|---|---|---|---|
| n/a | Each Scraping API supports a number of targets. This parameter is always required, along with either See targets supported by SERP Scraping APIs for examples. |
| |
|
|
| Enable JavaScript rendering. |
|
|
| auto-randomized | The geographical location that the result depends on. – City location names ⚠️ When providing a country name, must be in Capital Case:
|
|
| n/a | Matched with domain parameter | This will change the search page web interface language (not the results). |
|
| n/a |
| Adds requests headers to the target request. | |
| n/a |
| Client cookie. Allows opening up pages as if the user is logged in. | |
| n/a |
| By default, user-provided cookies are not forwarded to the target. Set this parameter to |
|
| n/a |
| By default, user-provided headers are not forwarded to the target. Set this parameter to |
|
| n/a |
|
|
|
|
|
| Device type and browser. |
|
|
|
| When set to |
|
| n/a | Session to re-use the same IP for multiple requests for up to 10 minutes |
| |
| n/a | Used to make a POST request instead of GET |
| |
| n/a | Base64 encoded POST request body. Used when http_method is POST. |
| |
| n/a | Define one or more HTTP response codes you consider successful and want to get the content for. |
|
Updated 24 days ago