proxy
option on any request. Below is an example of using the residential_cdp
proxy for a crawl.
Different domains will need different proxies. You’ll typically want to use the cheapest proxy that can reliably access a site. Below is a table showing the proxies available, and their costs.
Proxy | Cost per GB | Loads assets? |
---|---|---|
none | $0.01 / GB | No |
datacenter | $0.01 / GB | No |
mobile | $0.50 / GB | No |
residential_cdp | $8.00 / GB | No |
residential_cdp_assets | $8.50 / GB | Yes |
Try multiple proxies
You can ask FetchFox to try multiple proxies at once. Simply pass in an array of strings as theproxy
parameter. FetchFox will launch concurrent visits for each proxy you pass in, and use the first valid response it gets.
Below is an example of running an extraction with multiple proxies.
Automatically pick a proxy
It can be time consuming to decide which proxy to use for each scrape. If you’d like FetchFox to automatically pick a proxy for you, just pass inauto
as the proxy parameter.
Below is an example of how to run a crawl that automatically picks a proxy. The same parameter can be used for all other endpoints like scrape and extract.