proxyRegion
Narrow a request to a US state or a city inside proxyCountry, instead of rotating anywhere in that country.
Pin a request to a US state or a city inside the country you already selected with
proxyCountry.
By default a request with proxyCountry can exit anywhere in that country — two calls a minute apart can come from different cities. proxyRegion narrows that to a single state or city, which matters when the page you are scraping changes by location: retail pricing, delivery estimates, stock, and local search results.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
proxyCountry |
string | Yes | The country, exactly as listed in proxyCountry. Required — proxyRegion is ignored without it. |
proxyRegion |
string | No | A US state (name or two-letter code) or a city name. Omit it to keep the current behaviour: rotating anywhere in the country. |
Spacing, casing and punctuation are normalised, so Los Angeles, los angeles and LosAngeles are the same request.
Request
Pin to a city:
Pin to a US state, by name or by two-letter code — California and CA are equivalent:
Pin to a US city:
Notes
Leaving it out changes nothing. Requests without proxyRegion behave exactly as they did before the parameter existed.
In the US, a state wins over a same-named city. New York, Washington and Georgia are all read as states when proxyCountry is UnitedStates. Outside the US the same value is read as a city, so Georgia under proxyCountry: "Georgia" targets the city. To reach New York City specifically, target the state — its exits are concentrated there.
Two-letter codes are US states only. Under any other country a two-letter value is treated as a city name, which will almost certainly not match.
City coverage varies request to request. Cities come from the live residential pool, and a city that is available now may not be a minute later. An unavailable city fails the request rather than quietly falling back to the wider country, so anything pinning a city should retry rather than treat the first failure as final. States are more reliable than cities; countries are more reliable than states.
Verify the region when it matters. A region value that cannot be resolved may be dropped rather than rejected, which means a successful response is not by itself proof that the pin took effect. If your results depend on location, read the location back off the page — most sites that vary by region will tell you which one they served — instead of assuming it.
Which proxies it applies to. proxyRegion works on the standard rotating residential proxies and on premium proxies. It has no effect on mobile or datacenter proxies, which use a different pool. It is also dropped on the small number of requests that get routed to a backup pool automatically, which is another reason to verify rather than assume.
Related concepts
Go deeper in the Scrappey knowledge base:
- Residential proxy — the IP type geo-targeting runs on
- Residential vs datacenter — which proxy type to choose
- Proxy web scraping — how proxies route your requests