Amazon Proxies for US, UK and EU Marketplaces

You reduce them; you don't switch them off, and you don't solve them. A CAPTCHA page is Amazon telling that IP or session to slow down: treat it as a stop signal, not something to get past. Don't use CAPTCHA-solving services or retry loops. First, know what each answer means:

Do you need to scrape at all? For your own seller catalog, the Selling Partner API answers without store pages. Its getCatalogItem operation (GET /catalog/2022-04-01/items/{asin}, with marketplaceIds) returns an item's catalog data, such as summaries, attributes, images and sales ranks, at a rate of 2 requests per second with a burst of 2 (reference). The Associates program has its own product data API. Scrape public store pages only for what those APIs don't give you.

For public product pages, in this order:

1. Measure before you scale. On the Easy Trial (1 GB for $2.95, about 1,000 product pages at an example 1 MB each), fetch 100 product pages with rotation and 100 inside one sticky session, and count the CAPTCHA pages in each. Keep the setup with fewer.
2. Use residential IPs in the marketplace's country, a new IP per product page, so no single IP carries the load.
3. Pace requests per IP, with no bursts. Start slow and raise the rate only while your CAPTCHA count stays near zero.
4. Send real browser headers (User-Agent, Accept-Language) and keep cookies within a session; a bare script request stands out.
5. Keep one sticky session per postcode, so the IP and the delivery location stay consistent.
6. Fetch only the HTML, with no images or scripts: fewer requests per page and less traffic.
7. Stop and back off at the first CAPTCHA page. When they rise, slow down before you add IPs.

No proxy makes CAPTCHAs disappear. Amazon's Conditions of Use limit automated access to its store; collect only public pages, and read what Amazon's terms allow.

Rotating residential. Mobile IPs also work, at $0.50/GB more, but residential is enough for Amazon's web pages; datacenter IP ranges are easy to recognize as servers.

Links: Mobile proxies · Datacenter proxies · Static residential (ISP) proxies. Rotating datacenter proxies cover the same countries as residential; dedicated ISP and datacenter IPs come in the countries their order form lists, which follow stock

What to check in any Amazon proxy offer:

• residential IPs in each marketplace country you need, not only the US;
• city targeting, because delivery options differ inside a country;
• sticky sessions long enough for a full run through search results;
• a per-GB price you can start small with, and traffic that does not expire.

ProxyField covers all 4: 12 marketplace countries in the table above, city targeting, sticky sessions up to 36 h, and an entry of 1 GB with traffic that never expires.

Rotate per request for independent product pages; hold a sticky session (30 s to 36 h; presets 1, 5, 10, 30 min, 1, 3, 6 h) when you set a delivery postcode, page through search results or keep a cart.

Amazon prices and delivers by the "Deliver to" location saved in your session. Set it once inside a sticky session in that country, then load the pages you need before the session ends. The proxy picks the country, region or city; Amazon's "Deliver to" box sets the postcode.

More in Rotating proxies and sticky sessions.

ProxyField has 16.6M+ residential IPs in the United Kingdom across 640+ UK cities. In short: a UK IP, one sticky session per postcode, the postcode entered once in "Deliver to", and a stop at the first CAPTCHA page.

ZIP and postcode targeting is not a proxy option, so the postcode always comes from Amazon's own box.

1. Open a sticky session on a UK IP, in the city nearest the postcode if it matters, with a preset long enough for the run (10 or 30 min; up to 36 h). The full username is <login>-country-<cc>-region-<region>-city-<city>-session-<id>-ttl-<seconds>, as in <login>-country-us-region-new_york-city-new_york-session-he9f2qga-ttl-600; every part after the login is optional and ttl is 30 to 129,600 seconds.
2. Open amazon.co.uk and enter the postcode once in the "Deliver to" box.
3. Load your product or search pages inside that session, at a modest pace, and record the price and the delivery line (delivery cost, date and seller) for each ASIN.
4. At the first CAPTCHA page, stop. Pause that session, then resume at a lower rate; retrying at once brings more of them.
5. Repeat per postcode in a new sticky session, so each postcode keeps its own IP and cookies.

Cost of one postcode check (example inputs, measure yours): 100 UK product pages at 1 MB each use about 0.1 GB, or about $0.30 at $2.95/GB. Ten postcodes are about 1 GB, the size of the Easy Trial.

If you'd rather not run the sessions yourself, the Amazon Scraper API fetches Amazon product and search pages for $0.60 per 1,000 successful results, from $0.30 at volume. Amazon's Conditions of Use limit automated access to its store; collect only public pages (what Amazon's terms allow).

Pages × page size. Measure one product page through the proxy, multiply by your checks, and price it with the tier for that volume.

At 1 MB per page, 1,000 pages use about 1 GB; at 500 KB per page, about 0.5 GB.

Worked example (example inputs, measure yours):

• 2,000 ASINs × 1 check a day × 30 days = 60,000 pages a month.
• At an example 1 MB of HTML per page, that is 60 GB → 60 × $2.65 = $159.00 (50–99 GB tier; the tier rate applies to the whole purchase).
• At an example 500 KB per page, the same job is 30 GB → 30 × $2.79 = $83.70 (10–49 GB tier).

Cheaper than the big brands' $4/GB at every volume: residential proxies cost $2.95/GB for 1 GB and fall to $1.95/GB from 1,000 GB, with no subscription.

All purchases are final. In return, your traffic never expires: what you buy stays on your balance until you use it.

Blocking images and scripts and fetching only the HTML keeps traffic down. You pay in crypto (USDT, BTC, ETH or 10 other coins). All tiers are on Pricing per GB.