Parameters
All Scraper APIs support the following parameters
Parameter | Default value | Description |
---|---|---|
target | google_search | Each Scraping API supports a number of targets. This parameter is always required, along with either url or query .See targets supported by SERP Scraping APIs for examples. |
url | Direct URL (link) to a page you want to scrape. | |
query | A query used for the specific target. | |
geo | The geographical location that the result depends on. – City location names – State names – Country names – Coordinates and Radius – Google’s Canonical – Location Name. Read more here. | |
locale | Matched with domain parameter | This will change the search page web interface language (not the results). Example: – en-US – en-GB |
headers | Adds requests headers to the target request. | |
cookies | Client cookie. Allows opening up pages as if the user is logged in. | |
force_cookies | By default, user-provided cookies are not forwarded to the target. Set this parameter to true to override this behaviour. | |
domain | com | com, co.uk, fr, etc. |
device_type | desktop | Device type and browser. Supported: – desktop – desktop_chrome – desktop_firefox – mobile – mobile_android – mobile_ios |
parse | false | 'true' will return parsed output in JSON format. Leave blank for HTML – not all data sources can be parsed. |
headless | Enable JavaScript rendering. Supported: – html – png | |
session_id | Session to re-use the same IP for multiple requests for up to 10 minutes | |
http_method | Used to make a POST request instead of GET | |
payload | Base64 encoded POST request body. Used when http_method is POST. | |
successful_status_codes | Define one or more HTTP response codes you consider successful and want to get the content for. |
Updated 9 days ago