Amazon Scraper API

Best Proxies for Amazon Scraping in 2026: Compared

Updated at

The Answer

The best proxies for Amazon scraping in 2026 are country-matched rotating residential proxies from an established provider, with mobile proxies saved for the most protected pages. Datacenter proxies get blocked fast. Amazon’s WAF sorts traffic by ASN before the HTTP layer even runs, and cloud ASNs land in the suspicious pile. Residential pools from Bright Data, Oxylabs, Decodo, Webshare, or IPRoyal hold up on product detail pages at list prices between about $1.40 and $8 per GB, depending on provider and volume (checked October 2026). If you’d rather not manage proxies at all, the Amazon scraper API bundles the residential pool, rotation, and retries for $0.90 per 1,000 successful requests, with 1,000 free requests on signup.

Why Does Amazon Need Special Proxies?

Amazon needs special proxies because its WAF (Web Application Firewall) classifies incoming traffic by ASN (Autonomous System Number) in the first packet, before it looks at a single HTTP header. The ASN names the network operator. That’s enough for Amazon to tell commercial clouds (DigitalOcean, AWS itself, Linode, Hetzner, OVH) apart from residential ISPs like Comcast, Verizon, or Deutsche Telekom.

Requests from a commercial cloud ASN get scored on a harsher profile, with stricter rate limits, faster CAPTCHA escalation, and a lower bar before a challenge page replaces the product HTML. You’ve probably seen it happen. A Python script on a $5 DigitalOcean droplet works for a few minutes, then every request comes back as a robot check. Nothing in the script changed. Amazon had flagged the droplet’s ASN, and every request after that paid for it.

So the fix is routing through proxies whose IPs sit on residential or mobile ASNs, which Amazon’s WAF treats as low-risk by default.

What Are the Different Types of Proxies?

Four proxy types matter for Amazon scraping. Here they are from most to least reliable on Amazon:

  • Mobile proxies (carrier-grade NAT IPs from real cellular carriers) - the most reliable on every Amazon page type, seller profiles included, and the most expensive per GB.
  • Residential proxies (IPs from real home internet connections, sourced via opt-in SDKs in consumer apps) - reliable on product detail and search pages, a bit weaker on seller profiles. Roughly $1.40 to $8 per GB at the providers below.
  • ISP proxies (static IPs hosted in data centers but registered to consumer ISPs) - workable on product detail pages, though rotating residential holds up better at volume.
  • Datacenter proxies (commercial cloud IPs with no residential association) - blocked quickly on Amazon. Cheapest per GB, least useful.

Price follows what the IPs cost to acquire. A datacenter IP is a $5/month VPS, while a residential IP is a slice of bandwidth on a real home connection whose owner agreed to share it, and a mobile IP is a slice of somebody’s cellular plan. On reliability, the WAF’s ASN scoring is what counts, and to that scoring residential and mobile traffic reads as shoppers while a datacenter range reads as a bot.

Static vs Rotating Residential Proxies

Residential and mobile proxies both come in two configuration modes:

  • Rotating residential hands out a fresh IP for each request (or per session, configurable). Use it for high-volume scraping, since Amazon flags repeated requests from one IP for the same product.
  • Static residential (sticky sessions) keeps one IP for a set duration, anywhere from 10 minutes to 24 hours. Use it for paginated workflows that carry a session cookie across several requests.

For most Amazon product scraping, rotating wins. Paginated search results, or any flow that depends on Amazon’s session cookies? Go sticky.

Top 5 Proxy Providers for Amazon Scraping

These five providers publish their residential pricing openly. Prices and pool sizes come from each provider’s pricing page in October 2026.

ProviderResidential price per GBVolume price per GBStated residential pool
Bright Data$8 pay-as-you-go (list)$7 on the $499 plan (list)400M+ IPs, 195 countries
Oxylabs$6 (smallest tier)$2.50 above 1,000 GB175M+ IPs
Decodo$4 pay-as-you-go$2.75 on 100 GB, $2 on 1 TB115M+ IPs, 195+ locations
Webshare$3.50 (1 GB plan)$1.40 at 3,000 GBNot stated
IPRoyal$7.35 pay-as-you-go (1 GB)$1.84 at 10 TB+64M+ IPs

1. Bright Data

Bright Data runs one of the largest residential proxy networks, stating 400M+ rotating residential IPs across 195 countries. When one of its sub-pools gets flagged on Amazon, a network that size swaps fresh IPs in quickly.

Pricing: List price $8 per GB pay-as-you-go and $7 per GB on the $499 monthly plan. In October 2026 a promotional code on the pricing page cut those rates in half, so check what’s on offer when you buy.

Best for: Enterprise teams scraping at multi-TB scale who can negotiate custom plans, and compliance-conscious industries that need formal data-access agreements.

Trade-offs: The highest list price of the five. Bright Data also sells proxies and scraping products separately, which makes the total hard to predict.

2. Oxylabs

Oxylabs is a Lithuanian provider stating 175M+ residential IPs worldwide, with a large mobile pool next to it.

Pricing: $6 per GB on the smallest tier, dropping to $2.50 per GB above 1,000 GB.

Best for: Teams scraping plenty of e-commerce targets beyond Amazon, and EU-based teams who want an EU-headquartered vendor.

Trade-offs: A premium entry price. Proxies and the Web Scraper API are separate products, and a lot of production setups end up paying for both.

3. Decodo (formerly Smartproxy)

Decodo, which rebranded from Smartproxy in 2025, states 115M+ residential IPs in 195+ locations. It prices aggressively at both the small and the large end.

Pricing: $4 per GB pay-as-you-go, $2.75 per GB on the 100 GB plan, and $2 per GB on the 1 TB plan.

Best for: Mid-market teams scraping 100 GB to a few TB a month, and teams that want proxies and a scraping API from the same vendor.

Trade-offs: Its pool is smaller than Bright Data’s or Oxylabs’, so gaps can show up on niche city targets.

4. Webshare

Webshare is the budget pick, with the lowest volume price of the five. Expect $3.50 per GB on a 1 GB plan, falling to $1.40 per GB at 3,000 GB a month.

The rotation setup is basic. Webshare also says little about its residential pool. Still, for Amazon product detail pages at modest volume it’s a fair place to start. Heavy seller-profile scraping or Prime Day-level traffic is where a deeper pool earns its price.

Best for: Cost-sensitive teams, solo developers, and small consultancies.

Trade-offs: Little published detail on pool size and sourcing. Fewer enterprise features.

5. IPRoyal

IPRoyal states 64M+ residential IPs and lists its headquarters in the United Arab Emirates. You can buy residential traffic pay-as-you-go or as a monthly subscription.

Pricing: $7.35 per GB for a single GB pay-as-you-go, down to $1.84 per GB at 10 TB+, with subscriptions slightly cheaper ($7.00 down to $1.75).

Best for: Teams buying large volumes on a subscription.

Trade-offs: Small purchases are expensive, and the pool is smaller than the top three.

How Do You Choose Between Residential, ISP, and Mobile Proxies?

For Amazon scraping specifically, pick by the page and the volume.

For product detail page scraping at any volume: rotating residential. You get most of mobile’s reliability at a fraction of the price.

For paginated workflows that need session continuity: static residential or ISP proxies with sticky sessions. A fixed IP keeps the session cookies Amazon uses across requests intact.

For seller profiles, back-end search filters, and any page Amazon protects more aggressively: mobile proxies. Carrier IPs from real cellular networks carry the weakest detection signal.

For under 5,000 ASINs per month: Webshare or Decodo pay-as-you-go. At this volume the per-GB price decides it.

Above 100,000 ASINs per month: Bright Data, Oxylabs, or Decodo on a volume plan. Pool depth matters most at this size, because peak-season anti-bot escalations hit small pools hardest.

What Is the Cost of Proxies for Amazon Scraping?

Residential proxy costs scale in a straight line with bandwidth. An Amazon product detail page runs several hundred KB compressed, depending on category, and search result pages are heavier. For planning, assume 250 KB per scrape across a mixed workload.

Here’s what that works out to:

  • 10,000 ASINs at 250 KB = 2.5 GB. At $7 per GB residential = $17.50 per 10,000 requests.
  • 100,000 ASINs at 250 KB = 25 GB. At $4 per GB = $100 per 100,000 requests.
  • 1,000,000 ASINs at 250 KB = 250 GB. At $2.50 per GB = $625 per 1M requests.

Now the same volumes on a managed scraper API at $0.50 to $0.90 per 1,000 requests:

  • 10,000 ASINs at $0.90 per 1,000 = $9.
  • 100,000 ASINs at $0.90 per 1,000 = $90.
  • 1,000,000 ASINs at $0.50 per 1,000 (Custom) = $500.

Retries make the proxy bill worse. A blocked attempt still burns bandwidth, whereas a pay-per-success API bills only the requests that return data. Above roughly 50,000 requests a month the managed API is cheaper, and the gap widens once you count the engineering hours that go into keeping a DIY scraper alive. The Amazon product scraper API bundles the proxy, retry, and parsing layers, from $0.90 per 1,000 successful requests.

How Do You Integrate Residential Proxies in Python?

Most Python Amazon scrapers integrate residential proxies by pairing curl_cffi (for browser TLS fingerprint impersonation) with an HTTP-level proxy URL.

from curl_cffi import requests

PROXY_URL = "http://username:password@proxy.example.com:8080"

response = requests.get(
    "https://www.amazon.com/dp/B09HN3Q81F",
    impersonate="chrome",
    proxies={"http": PROXY_URL, "https": PROXY_URL},
    timeout=30,
)

Three lines in that snippet do the work:

  • impersonate="chrome" makes curl_cffi replay a real Chrome TLS handshake. Leave it out and Python’s default requests library sends a TLS fingerprint Amazon flags in the first packet, proxy or no proxy.
  • The proxies dict routes curl through the residential proxy. Providers issue credentials in username:password format.
  • The 30-second timeout gives slow responses room under load.

For country-matched routing, say a German IP for amazon.de, most providers pick the country through the username or a parameter in the proxy URL. The syntax differs per provider. Go by their documentation.

How Do You Rotate Residential Proxy IPs?

You rotate residential proxy IPs in one of two ways:

  • Per-request rotation (rotating residential): the provider returns a fresh IP for each new request. It’s the default on most rotating endpoints and the right call for high-volume product scraping.
  • Per-session rotation (sticky residential): the provider holds one IP for N minutes, configurable and typically 10 to 30. Use it for paginated workflows where session cookies need to survive.

Both get configured at the proxy URL level in Python, usually with a session ID in the username. On Amazon, per-request rotation covers most workloads. Only switch to sticky when a workflow needs it.

What Are Best Practices for Amazon Proxy Scraping?

Five habits move success rates on Amazon proxy scraping:

  • Match country to TLD. Scrape amazon.de through a German IP and amazon.co.jp through a Japanese one. A cross-country request is an easy anomaly for Amazon to catch.
  • Cap requests per IP. Keep any single residential IP at 3 to 5 requests per minute to amazon.com. Rotating endpoints included: check that your rotation logic enforces the cap.
  • Rotate User-Agents in lockstep with IPs. One User-Agent across thousands of IP rotations becomes a fingerprint of its own.
  • Back off before retrying. When Amazon serves a 429 or a challenge page, wait a few seconds, then retry on a fresh IP. Hammering straight away makes the block last longer.
  • Cache aggressively. Most product pages change a few times a day at most. A 30 to 60 minute cache cuts bandwidth, cost, and detection risk in one go.

FAQ

What’s the cheapest proxy provider for Amazon scraping?

Webshare has the lowest volume price of the providers above, $1.40 per GB at 3,000 GB a month, and Decodo’s $4 per GB pay-as-you-go is the cheapest small purchase. Go below that tier and you’re usually buying smaller pools with weaker IP hygiene, which makes the per-request math worse even at a lower per-GB price.

Do free proxies work for Amazon scraping?

No. Free proxy lists are mostly datacenter IPs Amazon already flags, plus hosts that vanish within minutes. Success rates against Amazon sit close to zero, and the hours lost to retries wipe out any savings.

Can I scrape Amazon without proxies?

Only at tiny volume: a few dozen requests a day from one home IP, and only product detail pages. Go past that and Amazon’s per-IP rate limit kicks in, flagging your home IP for hours or days. Any production workflow needs residential proxies or a managed scraper API.

How do I avoid getting blocked when scraping Amazon?

Combine four things: country-matched residential proxies, browser-impersonation TLS (via curl_cffi), conservative request rates (3 to 5 per minute per IP), and response caching. Our bypass Amazon CAPTCHA guide shows how to detect the challenge pages Amazon serves when a request is blocked.

Should I use mobile proxies or residential for Amazon?

Residential is the default, on cost. Mobile is the upgrade for harder targets such as seller profiles, back-end search filters, and any page Amazon protects more aggressively. It costs more per GB at every provider, so most teams keep it for the small share of their Amazon workload that actually needs it.

What’s the difference between scraping with proxies vs using an Amazon scraper API?

A scraper API wraps the proxy layer, the TLS-fingerprint layer, the retry layer, and the response-parsing layer into one HTTP endpoint. You pay per successful request instead of per GB of bandwidth, and when Amazon changes its anti-bot stack, the infrastructure work isn’t yours. Above roughly 50,000 requests a month, a managed API like the Amazon scraper API costs less than residential proxies plus engineering time. For smaller workloads where you want full control, raw residential proxies are still the right call.

Sources