A proxy for Amazon helps when Amazon's own APIs do not cover the job, such as price research without seller or affiliate access. For that, rotating residential addresses in the store's country spread the pace; a signed-in account needs one steady address. Bots that buy limited items fall outside Amazon's license, which leaves out robots. Amazon runs its own data routes for sellers and affiliates, and those come first below.
We read Amazon's developer documentation on October 23, 2026, and we sent amazon.com requests from our own servers in September and October 2026. We tested no proxy network for this page.
Do you need a proxy for Amazon at all?
Not when Amazon's own API covers your job. Sellers have the Selling Partner API. Its getItemOffersBatch call returns the lowest offers for up to 20 products, and its default rate is one call every 10 seconds. That comes to 7,200 products an hour:
These limits hold for one seller and one application. Amazon says they do not rise because you call more often, and that sellers with bigger needs may get higher ones. Catalog details without offers move faster: the catalog search takes 20 products a call at two calls a second.
Affiliates have the Creators API, which Amazon asks users of its old Product Advertising API to move to. It needs membership in Amazon Associates for that store and at least 10 qualifying sales in the past 30 days. Its GetItems call takes up to 10 products and can return the price of an offer. Our Amazon price tracker guide walks through both routes.
If you are neither a seller nor an affiliate with sales, Amazon offers you no data route, and the rest of this page applies.
What do Amazon's terms say?
The Conditions of Use set the rules of the store. The version of August 14, 2026, grants a license "to access and make personal and non-commercial use of the Amazon Services". It leaves out "any collection and use of any product listings, descriptions, or prices" and "any use of data mining, robots, or similar data gathering and extraction tools".
Amazon's robots.txt points the same way. In September 2026 it asked every crawler to stay out of the offer listings (/gp/offer-listing/) and the cart (/gp/cart), and it shut 99 named crawlers out of the whole site. On October 23, 2026, the reader we use for research honored that file and read no amazon.com page.
A proxy changes none of this. What the terms mean for you depends on where you are, what you collect and how you use it. This page does not give legal advice.
What did amazon.com do with our requests?
Both of our tests ran from servers in data centers, the kind of address a cheap proxy also gives you.
On September 16, 2026, a server in Germany sent amazon.com 102 requests. One every eight seconds passed, and so did a burst of 60 to one listing. The robot check came after about 100 requests in 11 minutes, and it was still there 44 minutes later. The pages also said "Deliver to France", a location we never chose, and the product's own price was missing.
On October 10, 2026, a server in the US sent seven requests, at least 10 seconds apart. Product, search and help pages came back whole. The home page, asked for with a browser's headers, came back as a JavaScript challenge from AWS WAF, Amazon's own web firewall.
Three lessons follow for anyone who sends requests to Amazon:
- Pace per address matters. The check came after a run of requests from one address, so spread them over time or over more addresses.
- Check the page, not the status code. The robot check came back with status 200. Our Amazon CAPTCHA guide shows how to tell each check apart.
- The delivery location shapes the page. Check the "Deliver to" line on every page you keep.
Which proxy fits which Amazon job?
| Your job | Amazon's own route | What a proxy adds |
|---|---|---|
| Watching offers as a seller | Selling Partner API, 7,200 products an hour in batches | Usually nothing |
| Product data for an affiliate site | Creators API, with 10 qualifying sales in 30 days | Usually nothing |
| Price research without seller or affiliate access | None | An exit in the store's country, and pace spread over many addresses |
| Signing in to your own account from a server | The site itself | One steady address in your country |
| Running several seller accounts | Amazon's seller rules decide | Nothing that changes those rules |
| Bots that buy limited items | None: the license leaves out robots | Not covered here |
Datacenter addresses are what our test servers had. At a slow pace they got whole product pages, so a few pages an hour may need no more than one datacenter or static address in the store's country. Our guide to datacenter vs residential proxies sets the two types side by side.
Rotating residential addresses fit volume. Each request can leave from a different residential address in the country you pick, so no single address carries the whole pace. Our guide what is a residential proxy explains the type.
A sticky session or a static ISP address fits an account you sign in to. Amazon says it may ask for an extra sign-in step when a sign-in looks different, and a new location is one of its examples. An address that changes with every request can make each sign-in look new.
Mobile addresses, at $1.50 per GB, are rarely needed. Nothing in our tests or in Amazon's documents calls for them.
How do you match a proxy to an Amazon store?
Amazon's Selling Partner API lists 23 marketplaces, and each one is a country: 4 in North America and Brazil, 16 in Europe, the Middle East, India and Africa, and 3 in the Far East. Amazon's help says a page shows availability and delivery speed for the selected delivery location. Until you choose one, Amazon picks it for you, and our German server got France.
So pick the exit country to match the store: Germany for amazon.de, the United Kingdom for amazon.co.uk, the United States for amazon.com. Then set the delivery location in the session with the "Deliver to" selector, and keep the cookies so it stays set. Check that line on each page before you trust its price.
Our Residential Lite targets by country, and Residential Premium adds state and city.
How many addresses do you need?
Size by pace. In our test, the check came after about 100 requests in 11 minutes from one address. Plan for well under that per address, and add addresses or time when you need more. With rotating residential you pay by the gigabyte, so you count traffic instead of addresses.
Two habits keep a long run honest:
- Count the robot checks. Rotation makes one blocked request cheap, so a run can lose pages without anyone noticing. Log every page that comes back as a check.
- Test an exit before a long run. Our proxy checker shows whether an address answers and where it exits, and how to check if a proxy is working explains each result.
The wider habits are in avoiding IP bans while scraping, and proxies for web scraping covers the basics this page builds on.
Can you use free proxies for Amazon?
For a test of your code, yes. For a job that runs every day, no. In our audit of public lists on September 9, 2026, 163 of 961 sampled entries relayed a request, 17.0 percent. Our page on free proxies for Amazon goes deeper. Our free proxy list is checked around the clock by our checker, and are free proxies safe covers what else to weigh.
Where HProxy fits
We sell proxies, so weigh this part with that in mind. For Amazon data beyond what one address carries, Residential Lite costs $0.50 for one GB, falling to $0.18/GB at 1,000 GB+, and the balance does not expire. For an account, one static address for a month costs $2.70 per IP as static ISP or $1.58 per IP as IPv4 datacenter. Our Amazon proxies page sets the types side by side, and pricing lists every plan.
What we could not find out
We could not read Amazon's seller rules on running more than one account: Seller Central's help pages showed our reader no text without JavaScript. We could not read amazon.com for this update either, because its robots.txt keeps our reader out, so the terms and robots.txt quoted here come from our reads of September 16 and October 10, 2026. The Creators API pages we read give no default rate. Our pace numbers come from one address on one day, and we tested no residential exit, so we cannot say how much later the check comes through one. Amazon changes its documents and limits without notice, so we will read every source again by January 23, 2027.
Sources
- Amazon Selling Partner API: Usage Plans and Rate Limits (modified September 9, 2026), the getItemOffersBatch and getCompetitiveSummary references (updated September 10, 2026) and Marketplace IDs, read through our server on October 23, 2026.
- Amazon's Selling Partner API model files on GitHub, amzn/selling-partner-api-models, read October 23, 2026.
- Amazon Associates: the Creators API introduction, the GetItems reference and the error codes, read October 23, 2026.
- Amazon, Conditions of Use, last updated August 14, 2026, read October 10, 2026.
- Amazon's robots.txt, read September 16, 2026, and Amazon's help on the delivery location selector, read the same day.
- Amazon Customer Service, About Multi-Factor Authentication, read October 10, 2026.
- Amazon Web Services, AWS WAF Developer Guide, AWS WAF token characteristics, read October 23, 2026.
- Our tests of amazon.com from our servers on September 16 and October 10, 2026, and our audit of public proxy lists of September 9, 2026.
- Our catalog: the residential, ISP and datacenter plans.
