Other Targets
This data type is universal and can be applied to any target. It accepts URLs along with additional parameters. You can find the list of all the available parameters in the URL section.
Overview
Below is a quick overview of all the available data source
values we support with other targets.
Source | Description | Structured data |
---|---|---|
| Submit any URL you like. | Depends on the URL. |
You can always write your own parsing instructions with Custom Parser feature and get structured data.
Query parameters
Parameter | Description | Default Value |
---|---|---|
source | Data source. More info. |
|
url | Direct URL (link) to Universal page | - |
| Device type and browser. The full list can be found here. |
|
| Geo location of proxy used to retrieve the data. The complete list of the supported locations can be found here. | |
| Locale, as expected in Accept-Language header. | |
| Enables JavaScript rendering. More info. | |
| Add this parameter if you are downloading images. Learn more here. |
|
| Base64-encoded | - |
| Pass your own cookies. | - |
| Indicate whether you would like the scraper to follow redirects (3xx responses with a destination URL) to get the contents of the URL at the end of the redirect chain. | - |
| Pass your own headers. | - |
| Set it to |
|
| If you want to use the same proxy with multiple requests, you can do so by using this parameter. Just set your session to any string you like, and we will assign a proxy to this ID, and keep it for up to 10 minutes. After that, if you make another request with the same session ID, a new proxy will be assigned to that particular session ID. | - |
| Define a custom HTTP response code (or a few of them), upon which we should consider the scrape successful and return the content to you. May be useful if you want us to return the 503 error page or in some other non-standard cases. | - |
| URL to your callback endpoint. More info. | - |
|
|
|
| Set the value to | - |
- required parameter
If you are observing low success rates or retrieve empty content, please try using additional "render": "html"
parameter in your request. More info about using render parameter can be found here.
Code examples
Simple request
In this example, the API will retrieve an e-commerce product page.
The example above uses the Realtime integration method. If you would like to use some other integration method in your query (e.g. Push-Pull or Proxy Endpoint), refer to the integration methods section.
All parameters
In this example, all available parameters are included (though not always necessary or compatible within the same request), to give you an idea on how to format your requests.
Parameter values
Geo_Location
Check the complete list of supported geo_location
values here.
Here is an example:
HTTP_Method
E-commerce Universal Scraper API supports two HTTP(S) methods: GET
(default) and POST
.
Last updated