Skip to main content
The proxy_country parameter forces ScrapeUnblocker to use an exit IP from a specific country. It’s accepted by all three public endpoints.

​
When you need it

Geo-fenced content

Streaming catalogs, e-commerce prices, news paywalls - many sites serve different content (or block entirely) based on the visitor’s country.

Localized SERPs

Google results differ dramatically by region. Use proxy_country on /serpApi to scrape SERPs as they appear in a given market.

Anti-bot geo rotation

Some bot-protection vendors apply tighter rules to certain country pools. Rotating through a friendly country can lift a 403.

Compliance

Verify that geo-blocking on your own site behaves as intended from a list of source countries.

​
Format

proxy_country is a two-letter ISO 3166-1 alpha-2 country code, lowercase.

​
Supported countries

If you request a country we don’t have proxies for, the request fails with HTTP 400 and the response body lists the countries that are available. Smaller pools (some countries have only a handful of IPs) still work, just with slower rotation. To confirm which country actually served a successful request, check the proxy_country field in the response (on /serpApi) or use get_cookies=true (on /getPageSource).

​
Examples

​
/getPageSource

​
/serpApi

​
/getImage

​
Verifying which country was used

/serpApi always returns the proxy_country actually used in its JSON response. For /getPageSource, set get_cookies=true to see which proxy served the request:
See cookies and sessions.

​
Tips

  • Match the country to the target. Scraping amazon.de from a US IP often returns the US redirect page. Use proxy_country=de.
  • Rotate on 403. If a target blocks one country, try another. Cycling us → gb → de resolves most rate-based blocks.
  • Expect higher latency on smaller pools. Less common countries have smaller proxy pools, which means longer rotation between requests.