Scraper API

Amazon Scraper API: Product and Search Pages as JSON, by Marketplace and ZIP

ProxyField's Amazon Scraper API returns Amazon product and search pages as JSON for $0.60 per 1,000 successful results, or $0.30 from 10,000 results in one purchase, and you are billed on successful results only. Tracking 50,000 ASINs a day is 1,500,000 results in a 30-day month: $450 a month ($15 a day) at $0.30, and that is the whole bill, with no plan or monthly fee on top. The API is designed to take amazon.com, amazon.co.uk, amazon.de or five more marketplaces with domain, and prices come back in USD on amazon.com, GBP on amazon.co.uk and EUR on amazon.de; a US delivery ZIP is set with zip_code. The API is in development: to start, contact sales.

Amazon scraper API per 1,000 successful results

Entry

$0.60

Volume, from

$0.30

Billed on successful results only.

QuestionShort answer
What do 50,000 ASINs a day cost?1,500,000 results a month: $450 at $0.30 per 1,000 ($15 a day), the price from 10,000 results in one purchase; $900 at the $0.60 entry price (pricing)
amazon.co.uk and amazon.de as well as amazon.com?Yes: set domain to com, co.uk, de, fr, it, es, ca or co.jp. Prices come back in USD, GBP, EUR, CAD or JPY, and each marketplace page is one result (marketplaces)
A US delivery ZIP code?In the design, yes: zip_code takes a 5-digit US ZIP on amazon.com only, such as 10001 or 90210, and delivery_location in the response confirms it ("New York 10001") (ZIP codes)

The same 50,000 ASINs a day, four ways:

RouteWhat you pay a monthWhat you handle
Amazon Scraper API$450 at $0.30 ($900 at the $0.60 entry price)Nothing: failed pages are not billed
Web Scraping API, plain HTTP$750 at $0.50, $300 at $0.20Parsing the HTML yourself
Web Scraping API, JS rendering$3,000 at $2.00, $1,500 at $1.00Parsing the HTML yourself
Your own scraper on residential proxiesAt an example 300 KB per page: 450 GB, $1,030.50 at $2.29/GBParsing, retries, servers; failed pages still use traffic
Features

Amazon data you get

The API returns 2 kinds of Amazon pages, parsed into JSON: product pages and search result pages. Every field is always in the response; one the page does not show comes back as null or an empty list.

A product page, by ASIN or product URL
The product page, parsed: ASIN and parent ASIN, title, brand, price, list price, currency, discount, coupon, stock line, Prime, delivery options and the delivery location, the Buy Box seller (name, ID, fulfilled by Amazon), the number of other sellers, rating, number of ratings, Best Sellers Rank, categories, bullet points, description, images, variations and product details
A search, by keyword
The search results page, parsed: per product its position (organic and sponsored), ASIN, title, URL, image, price, list price, rating, number of ratings, "bought in past month", Prime, Amazon's Choice and Best Seller labels; plus the last page and the total results
A category results page, by URL
The same fields as a search; page goes up to 20 and sort_by sets the order
A best-sellers list
Not an input of this API: fetch the list with the Web Scraping API, then each product by ASIN

All of these come parsed: the product's price as a number with its currency, the Buy Box seller, the rating and the number of ratings, and the Best Sellers Rank per category. Need another Amazon page or another store? The Web Scraping API fetches any URL for $0.50 per 1,000 successful results over plain HTTP, from $0.20 at volume.

Pricing

Pricing: $0.60 per 1,000 results, from $0.30

The Amazon Scraper API costs $0.30 per 1,000 successful results from 10,000 results in one purchase, and $0.60 per 1,000 below that; you are billed on successful results only, so a page that fails or is blocked costs nothing. One result is one product page or one search results page; each further results page (page=2 …) is one more result, and an ASIN with no product page is not billed. There is no plan, subscription or monthly fee on top: you pay from the same crypto balance as proxies, and the balance never expires.

What is not billed: error responses, blocked and timed-out requests, our internal retries, and an ASIN with no product page. (On the Web Scraping API, a target's 404 or 410 is a billed result; on this API, a missing product page is not.)

Per purchase, not per month: the $0.30 price applies to any purchase of 10,000 results or more. One top-up of 1,500,000 results for the month is priced at $0.30, and so is a daily top-up of 50,000; a top-up of 9,000 is priced at $0.60.

Results a month = ASINs × checks per day × 30. Cost = results ÷ 1,000 × the price.

Amazon scraper API per 1,000 successful results

Entry

$0.60

Volume, from

$0.30

Billed on successful results only.

Read moreShow less
Workload (one product page per ASIN per day)Results a monthPer month at $0.30Per day at $0.30Per month at $0.60
1,000 ASINs, daily30,000$9$0.30$18
10,000 ASINs, daily300,000$90$3$180
50,000 ASINs, daily1,500,000$450$15$900
100,000 ASINs, daily3,000,000$900$30$1,800

How the 50,000-ASIN bill grows with the real workload:

ChangeResults a monthPer month at $0.30
Twice a day instead of once3,000,000$900
The same ASINs on amazon.com, amazon.co.uk and amazon.de4,500,000$1,350
Plus 500 keywords, one search page each, daily+15,000+$4.50

Every row in the first table is above 10,000 results a month, so a month bought in one purchase gets the $0.30 price; the 1,000-ASIN row also gets it with one purchase of 30,000 results. Each marketplace page is its own result, and so is each search results page.

The four-way table at the top compares the routes for 50,000 ASINs a day. Measure your own page size on 10 pages before you budget the proxy route; traffic math in general is on proxies for web scraping.

Testing before volume: the APIs are paid from the shared balance, topped up from $2.95; there is no separate test volume. All prices: pricing.

Locations

Marketplaces: amazon.com, amazon.co.uk, amazon.de and others

Yes: ProxyField's Amazon Scraper API pulls prices from amazon.co.uk and amazon.de as well as amazon.com, with domain set to co.uk, de or com, and 8 marketplaces in the first version. The same ASIN can have a different price, currency, seller, stock and delivery date on each one, so store the marketplace and the currency with every price. The same ASIN on three marketplaces is three requests and three results, $0.90 per 1,000 ASINs at $0.30.

Read moreShow less
MarketplacedomainPrice currencylocale: a language the marketplace offers, such as
amazon.comcomUSDen_US, es_US
amazon.co.ukco.ukGBPen_GB
amazon.dedeEURde_DE
amazon.frfrEURfr_FR
amazon.ititEURit_IT
amazon.esesEURes_ES
amazon.cacaCADen_CA
amazon.co.jpco.jpJPYja_JP
Delivery postcode on amazon.co.uk, amazon.de and the others––not part of the first version: zip_code is a US ZIP on amazon.com only
Shell
# The same ASIN on amazon.com, amazon.co.uk and amazon.de (the API's design; access through Contact sales)
for d in com co.uk de; do
  curl https://api.proxyfield.io/v1/amazon/product -H "Authorization: Bearer <api_key>" -H "Content-Type: application/json" \
    -d "{\"asin\": \"B0EXAMPLE7\", \"domain\": \"$d\"}"
done

Each response carries "currency" (USD, GBP or EUR) next to "price", and parameters.domain repeats the marketplace you asked for. locale is optional; leave it out for the marketplace's own default. The amazon.co.uk response, shortened (an example of the design, not live data):

JSON
{
  "metadata": {"api": "amazon_product", "status": "success", "billed": true},
  "parameters": {"asin": "B0EXAMPLE7", "domain": "co.uk", "zip_code": null, "locale": "en_GB"},
  "product": {"asin": "B0EXAMPLE7", "price": 79.99, "currency": "GBP", "stock": "In stock", "buybox": {"seller_name": "Example Home UK"}}
}

With the Web Scraping API, the marketplace is the URL you send, for $0.50 per 1,000 successful results over plain HTTP, from $0.20:

Shell
# The requests the Web Scraping API takes (access through Contact sales)
curl https://api.proxyfield.io/v1/scrape -H "Authorization: Bearer <api_key>" -H "Content-Type: application/json" \
  -d '{"url": "https://www.amazon.de/dp/B0EXAMPLE00", "country": "de"}'
curl https://api.proxyfield.io/v1/scrape -H "Authorization: Bearer <api_key>" -H "Content-Type: application/json" \
  -d '{"url": "https://www.amazon.co.uk/dp/B0EXAMPLE00", "country": "gb"}'

With your own scraper on ProxyField proxies, use a residential IP in the marketplace's country:

MarketplaceCountryPrices inProxyField residential IPs there
amazon.comUnited StatesUSD61.2M+, all 50 states, 2,800+ cities
amazon.co.ukUnited KingdomGBP16.6M+, 640+ cities
amazon.deGermanyEUR20.2M+, 980+ cities
amazon.frFranceEUR8.3M+, 170+ cities
amazon.esSpainEUR13.7M+, 690+ cities
amazon.itItalyEUR10.2M+, 210+ cities
amazon.nlNetherlandsEUR3.2M+, 110+ cities
amazon.caCanadaCAD5.5M+
amazon.co.jpJapanJPY3.3M+
amazon.inIndiaINR42.6M+, 1,100+ cities
amazon.com.mxMexicoMXN26.1M+
amazon.com.brBrazilBRL36.8M+
amazon.com.auAustraliaAUD4.1M+, 140+ cities

The IP figures are ProxyField's proxy pool for your own scraper, not a list of what the API parses. Country key in the username for non-US IPs: the two-letter country code in lowercase, as in -country-de. Which IP country for which marketplace, step by step: proxies for Amazon.

Amazon US ZIP code targeting: zip_code, confirmed in delivery_location

ProxyField's Amazon Scraper API is designed with a zip_code parameter for US ZIP codes on amazon.com only: a 5-digit ZIP such as 10001 (New York) or 90210 (Beverly Hills), at the same $0.60 per 1,000 successful results, or $0.30 from 10,000 in one purchase. The API is in development (Contact sales). In the design, the price, Buy Box, stock and delivery date in the result are the ones Amazon shows for that "Deliver to" ZIP, and delivery_location in the response confirms the ZIP that was applied. Postcodes on amazon.co.uk, amazon.de and the other marketplaces are not part of the first version.

What to check in any Amazon scraper API that claims to set the delivery ZIP code, with ProxyField's answer:

What to checkWhy it mattersProxyField's Amazon Scraper API
A ZIP parameterAmazon prices by the "Deliver to" ZIP, not by the IP alonezip_code, 5 digits
Which ZIPs and marketplaces it acceptsA parameter that only works on one marketplaceUS ZIP codes on amazon.com (domain=com)
A response field that confirms the ZIPWithout it you cannot tell a default location from yoursdelivery_location, such as "New York 10001"
BillingZIP checks multiply resultsOne result per page and ZIP, billed on success only
Read moreShow less

Two ZIPs, two requests, two results:

Shell
# The API's design (access through Contact sales)
curl https://api.proxyfield.io/v1/amazon/product -H "Authorization: Bearer <api_key>" -H "Content-Type: application/json" \
  -d '{"asin": "B0EXAMPLE7", "domain": "com", "zip_code": "10001"}'
curl https://api.proxyfield.io/v1/amazon/product -H "Authorization: Bearer <api_key>" -H "Content-Type: application/json" \
  -d '{"asin": "B0EXAMPLE7", "domain": "com", "zip_code": "90210"}'
zip_code 10001 -> "price": 89.99, "stock": "In Stock",       "delivery": [{"type": "FREE delivery", "date": "Wednesday, October 29"}], "delivery_location": "New York 10001"
zip_code 90210 -> "price": 94.50, "stock": "Only 3 left in stock", "delivery": [{"type": "FREE delivery", "date": "Friday, October 31"}], "delivery_location": "Beverly Hills 90210"

The two responses are shortened, invented examples of the design, not live data: they show the kind of difference a ZIP makes. Compare price, stock and delivery per ZIP; a delivery_location that does not show your ZIP means it was not applied.

10 ZIPs for one ASIN in one batch. A batch takes up to 1,000 requests of one API; params are shared and each item overrides them, a signed callback arrives per finished job, and results are kept for 48 hours (jobs and batches):

Shell
# The API's design (access through Contact sales)
curl https://api.proxyfield.io/v1/jobs/batch -H "Authorization: Bearer <api_key>" -H "Content-Type: application/json" -d '{
  "api": "amazon_product",
  "params": {"asin": "B0EXAMPLE7", "domain": "com"},
  "items": [{"zip_code": "10001"}, {"zip_code": "90210"}, {"zip_code": "60601"}, {"zip_code": "77002"}, {"zip_code": "33101"},
            {"zip_code": "98101"}, {"zip_code": "02108"}, {"zip_code": "30303"}, {"zip_code": "80202"}, {"zip_code": "85001"}],
  "callback_url": "https://example.com/amazon-hook"
}'

Ten ZIPs are ten results: $0.006 at $0.60 per 1,000. Pricing 1,000 ASINs across 10 ZIP codes once a day is 300,000 results a month: $90 at $0.30, sent as 10 batches of 1,000 requests a day.

What the ZIP changes on the same ASIN:

On the product pageWhat changes by ZIP
Price and Buy Box sellerthe offer Amazon picks for that delivery area
Other sellers' offerswhich sellers ship to that ZIP
Stock"In Stock", "Only N left" or "Currently unavailable" for that area
Delivery date and feewhen and at what cost the item reaches that ZIP

Setting the ZIP with your own scraper

Amazon stores the "Deliver to" ZIP in the session, and the IP only sets the first guess, so set the ZIP once per session and keep one sticky US-city IP while you load the pages. The check: the "Deliver to" line (#glow-ingress-line2) shows the city and ZIP Amazon applied, such as "New York 10001". If it still shows your IP's city, the ZIP did not stick.

ProxyField proxies target the country, region and city, not a ZIP code: pick the US city near your ZIP for the IP, and let Amazon's box set the ZIP itself. With your own scraper, in 5 steps:

  1. Open a browser through the gateway with a US-city IP and one sticky session.

  2. Load amazon.com and click the "Deliver to" box (#nav-global-location-popover-link).

  3. Type the ZIP in #GLUXZipUpdateInput and click Apply (#GLUXZipUpdate).

  4. Reload, then read #glow-ingress-line2 to confirm the ZIP.

  5. Load your product pages in the same session; start a new session for the next ZIP.

A Playwright version (Amazon's element IDs change from time to time):

Python
from playwright.sync_api import sync_playwright

ZIP = "10001"
with sync_playwright() as p:
    browser = p.chromium.launch(proxy={
        "server": "http://gate.proxyfield.io:7000",
        "username": "<login>-country-us-city-new_york-session-he9f2qga-ttl-1800",  # one sticky IP for 30 min
        "password": "<password>",
    })
    page = browser.new_page()
    page.goto("https://www.amazon.com/")
    page.click("#nav-global-location-popover-link")   # the "Deliver to" box
    page.fill("#GLUXZipUpdateInput", ZIP)
    page.click("#GLUXZipUpdate")
    page.wait_for_timeout(2000)
    page.reload()
    print("Deliver to:", page.inner_text("#glow-ingress-line2"))  # should show the ZIP you set
    page.goto("https://www.amazon.com/dp/B0EXAMPLE00")  # replace with a real ASIN
    print(page.title())
    browser.close()

Sticky-session username: -region-<region>, -session-<id> and -ttl-<seconds> (30 to 129,600 seconds, 20 minutes by default) after the location, as in <login>-country-us-region-new_york-city-new_york-session-he9f2qga-ttl-600. What it costs in traffic: at an example 300 KB per page, 1,000 product pages for one ZIP are about 300 MB, under $1 at $2.95/GB. Test several ZIP codes and check the "Deliver to" line on each page before you trust the prices.

Getting started

Sample request and response

You send an ASIN or a keyword and get the page back as JSON. The API takes a POST with your API key in an Authorization: Bearer <api_key> header and a JSON body, at one of two addresses. Parameter reference: API documentation.

OperationAddressParameters
Product pagehttps://api.proxyfield.io/v1/amazon/productasin or url; domain, zip_code, locale
Search or category pagehttps://api.proxyfield.io/v1/amazon/searchquery or the url of a search or category results page; page (1 to 20), sort_by (featured, price_low_to_high, price_high_to_low, average_review, newest, best_sellers); domain, zip_code, locale
Shell
# The request the Amazon Scraper API takes (access through Contact sales)
curl https://api.proxyfield.io/v1/amazon/product \
  -H "Authorization: Bearer <api_key>" \
  -H "Content-Type: application/json" \
  -d '{"asin": "B0EXAMPLE7", "domain": "com", "zip_code": "10001"}'
Python
# Python requests: the same product page
import requests

resp = requests.post(
    "https://api.proxyfield.io/v1/amazon/product",
    headers={"Authorization": "Bearer <api_key>"},
    json={"asin": "B0EXAMPLE7", "domain": "com", "zip_code": "10001"},
    timeout=130,
)
p = resp.json()["product"]
print(p["title"], p["price"], p["currency"], p["buybox"]["seller_name"])

Example response for one product (shortened; the full one also carries categories, bullet points, the description, images, variations and product details):

JSON
{
  "metadata": {"id": "req_e16b4c8f2a7d903e", "api": "amazon_product", "status": "success", "billed": true},
  "parameters": {"asin": "B0EXAMPLE7", "url": null, "domain": "com", "zip_code": "10001", "locale": "en_US"},
  "product": {
    "asin": "B0EXAMPLE7",
    "parent_asin": "B0EXAMPLE0",
    "title": "Example Stainless Steel Burr Coffee Grinder, 40 Grind Settings",
    "brand": "Example Home",
    "price": 89.99,
    "price_strikethrough": 109.99,
    "currency": "USD",
    "stock": "In Stock",
    "is_prime": true,
    "delivery_location": "New York 10001",
    "buybox": {"seller_name": "Example Home Store", "seller_id": "A1EXAMPLESELLER", "fulfilled_by_amazon": true},
    "other_sellers_count": 3,
    "rating": 4.4,
    "reviews_count": 5873,
    "sales_rank": [{"rank": 412, "category": "Kitchen & Dining"}, {"rank": 7, "category": "Burr Coffee Grinders"}]
  }
}

Reviews, prices and best sellers

Amazon reviews

A product page shows the rating, the review count and the reviews Amazon displays on it. The Amazon Scraper API returns the product page's rating and number of ratings; review pages are not part of it, and neither are the review texts. For a whole category:

  1. Get the ASINs from the category or best-sellers page.

  2. Fetch the product page for each ASIN and read the rating, review count and reviews.

Collect public reviews only, without logging in.

Prices and offers

The product page carries the current price, the list price, the Buy Box seller and the offers from other sellers. The API parses the price, the list price, the discount, any coupon, the Buy Box seller and the number of other sellers; the list of other sellers' offers is not part of it. To compare prices across many stores, use the Web Scraping API on each store's pages; more in price scraping.

Best sellers

A best-sellers list is not an input of the Amazon Scraper API; a category results page is, with sort_by set to best_sellers. The Web Scraping API fetches any best-sellers page; this API then fetches each product by ASIN.

When Amazon blocks a request

A page that Amazon blocks, or that fails for any other reason, is not billed: you pay only for successful results. In general, Amazon product data sits in the page HTML, so most product pages can be read without a headless browser.

Compare

Official Amazon APIs or scraping?

Amazon's official APIs serve specific groups. The Creators API (formerly the Product Advertising API) is for Amazon Associates, and the Selling Partner API is for sellers and vendors and mostly covers their own listings, orders and inventory. Both need an approved account and have usage limits. A scraper API reads the public product pages instead, for any ASIN.

ItemCreators APISelling Partner APIAmazon Scraper API
Who can use itApproved Amazon AssociatesRegistered sellers, vendors and approved developersProxyField customers
Which dataProduct data for affiliate linksMostly the account's own listings, orders and inventoryAny public product or search page
LimitsRequest limits set by AmazonRequest limits set by AmazonBilled per 1,000 successful results
CostSet by AmazonSet by Amazon$0.60 per 1,000, from $0.30
Use cases

What teams use it for

  • Price and Buy Box monitoring for each ASIN.
  • Review and rating analysis for your products and your category.
  • Assortment and best-seller research.
  • MAP checks: sellers' prices against your minimum advertised price.
  • Catalog enrichment with public titles, brands and attributes.

Writing or manipulating reviews is not allowed.

Scrape Amazon with Python and ProxyField proxies

You can fetch Amazon product pages with Python requests and parse them with Beautiful Soup, but Amazon limits requests per IP, so rotate residential IPs and keep the request rate low. ProxyField gives you a new IP on every request or a sticky session from 30 s to 36 h, with country, region and city targeting.

ProxyField residential proxies cost $2.95/GB for 1 GB and from $1.95/GB at volume, with no subscription; the traffic never expires, and all purchases are final. You get 412M+ residential IPs in 195+ countries and 21,000+ cities, over HTTP, HTTPS or SOCKS5.

Python
import requests
from bs4 import BeautifulSoup

proxy = "http://<login>-country-us-city-new_york:<password>@gate.proxyfield.io:7000"
url = "https://www.amazon.com/dp/B0EXAMPLE00"   # replace with a real ASIN
resp = requests.get(url, proxies={"http": proxy, "https": proxy},
                    headers={"User-Agent": "Mozilla/5.0", "Accept-Language": "en-US"},
                    timeout=30)
soup = BeautifulSoup(resp.text, "html.parser")
title = soup.select_one("#productTitle")
print(resp.status_code, title.get_text(strip=True) if title else "no title (blocked or changed layout)")
  • Browsers: Puppeteer and Playwright work the same way: pass the gateway, username and password in the proxy settings.
  • No-code: not in the first version of the API
  • Start small: the Easy Trial is 1 GB of residential traffic for $2.95, with no minimum purchase and no subscription. The traffic never expires, and all purchases are final.

More: proxies for Amazon and residential proxies from $1.95/GB.

Also from ProxyField

More scraper APIs

FAQ

Amazon Scraper API FAQ

24/7 support by live chat, including help with setup and integration.

How much does an Amazon scraper API cost?

ProxyField's Amazon Scraper API costs $0.60 per 1,000 successful results, or $0.30 from 10,000 results in one purchase, and you are billed on successful results only. Checking 10,000 ASINs a day is 300,000 results a month: $90 at $0.30. There is no subscription or monthly fee.

What does an Amazon scraper API charge per 1,000 results if I track about 50,000 ASINs every day?

ProxyField's Amazon Scraper API is priced at $0.30 per 1,000 successful results at this volume: 50,000 ASINs a day is 1,500,000 results in a 30-day month, so $450 a month ($15 a day). The $0.30 price applies to any purchase of 10,000 results or more ($0.60 below that), so one monthly top-up or daily top-ups of 50,000 both qualify. Error responses, blocked and timed-out requests and internal retries are not billed, and no plan or monthly fee sits on top, so $450 is the whole bill. Checking twice a day doubles it to $900, and each extra marketplace adds $450.

Can an Amazon scraper API pull prices from Amazon.co.uk and Amazon.de as well as Amazon.com?

Yes: ProxyField's Amazon Scraper API, in development, is designed to take domain set to com, co.uk, de, fr, it, es, ca or co.jp, 8 marketplaces in the first version, for $0.60 per 1,000 successful results, or $0.30 from 10,000 in one purchase. Prices come back in USD on amazon.com, GBP on amazon.co.uk and EUR on amazon.de, and the same ASIN can show a different price, seller and delivery date on each, so store the marketplace with every price. Each marketplace page is one result: one ASIN on three marketplaces is three results.

Which Amazon scraper APIs let me set a US delivery ZIP code to get local prices and availability?

ProxyField's Amazon Scraper API is designed for it: zip_code takes a 5-digit US ZIP on amazon.com only, such as 10001 or 90210, and delivery_location in the response confirms it ("New York 10001"), at $0.60 per 1,000 successful results, or $0.30 from 10,000 in one purchase; the API is in development, through Contact sales. In any API, check for three things: a ZIP parameter, which marketplaces it accepts, and a response field that confirms the ZIP. US ZIP codes on amazon.com only in the first version; with your own scraper, set the ZIP in Amazon's "Deliver to" box on one sticky US-city IP.

What's the best Amazon scraper API for prices, reviews and sellers?

ProxyField's Amazon Scraper API, in development through Contact sales, is designed to return Amazon product and search pages parsed into JSON, with the price, list price, Buy Box seller, number of other sellers, rating and number of ratings, for $0.60 per 1,000 successful results, or $0.30 from 10,000 in one purchase. Review texts and the list of other sellers' offers are not part of it. When you compare APIs, check which fields come parsed, the marketplaces and ZIP codes you can set, and whether failed pages are billed.

Does Amazon have an official API for product data, or do I have to scrape it?

Yes, for specific groups: the Creators API for Amazon Associates and the Selling Partner API for sellers and vendors, which mostly covers their own listings and orders. Both need an approved account and have usage limits. A scraper reads the public pages for any ASIN.

How do I scrape Amazon reviews for every product in a category?

Collect the ASINs from the category or best-sellers page, then fetch each product page, which shows the rating, the review count and the reviews Amazon displays on it. Collect public reviews only, without logging in.

Is Amazon's API free?

Amazon sets access, limits and terms for its own APIs: the Creators API is for approved Amazon Associates, and the Selling Partner API for registered sellers and vendors. ProxyField's Amazon Scraper API is a paid alternative for any public product page, at $0.60 per 1,000 successful results.

How does an Amazon scraper API work?

You send a product (ASIN or URL) or a search keyword, and the API fetches the Amazon page and returns it parsed as JSON. Pages that fail are not billed. ProxyField's is designed this way and is in development, through Contact sales.

Why use a dedicated Amazon scraper API?

Because Amazon limits requests per IP and its pages change: an API takes care of fetching, and you pay only for successful results. At 50,000 ASINs a day it costs $450 a month at $0.30, against about $1,030 of residential traffic at an example 300 KB per page for your own scraper.

Show 14 more questionsShow fewer questions

How do I scrape Amazon with Python?

Fetch the product page with requests through rotating residential proxies and parse it with Beautiful Soup, as in the code on this page. Or call the Amazon Scraper API and skip the proxies and the parsing.

Do I need proxies to scrape Amazon?

With the API, no: it fetches the pages for you. With your own scraper, yes, because Amazon limits requests per IP; rotate residential IPs, such as ProxyField's from $1.95/GB, and keep the request rate low.

Does Amazon block web scraping?

Amazon limits automated requests and can block an IP that sends too many. Rotate IPs, keep the rate low and collect public pages only. With the API, a blocked page is not billed.

What is the rate limit for scraping Amazon?

Amazon publishes no limit for scraping; it limits requests per IP as it sees fit. Spread requests across rotating IPs, pace them per IP, and slow down when pages start to fail.

How do I scrape Amazon prices?

Fetch the product page for each ASIN: it carries the current price, the list price, the Buy Box seller and other sellers' offers. Set the marketplace and the delivery ZIP first, because both change the price. For other stores, use the Web Scraping API.

What data can I scrape from Amazon?

Amazon product pages and search result pages: a product by ASIN or product URL, and a search by keyword. A product page carries the ASIN, title, brand, price, availability, Buy Box seller, rating, review count and best-sellers rank, and ProxyField's Amazon Scraper API is designed to return all of them as JSON fields.

Can I scrape Amazon search results?

Yes: in the Amazon Scraper API's design, you send a keyword and get the Amazon search results page back, at $0.60 per 1,000 successful results; the API is in development, through Contact sales.

What is an ASIN and how do scrapers use it?

An ASIN is the 10-character ID Amazon gives each product, shown on the product page and in its URL. A scraper fetches a product by its ASIN, so the ASIN list is the input for price, review and catalog jobs.

Can I scrape Amazon best sellers?

Yes, in 2 steps: fetch the best-sellers page with the Web Scraping API, then each product by ASIN with the Amazon Scraper API.

Do I need a headless browser to scrape Amazon?

Usually not for product pages: the data is in the page HTML. A browser helps for one step, setting the "Deliver to" ZIP code in a session. With the API you run neither, and failed pages are not billed.

Can I scrape Amazon without coding?

The Amazon Scraper API is an API: you send an HTTP request, which takes a few lines of Python or one cURL command, as in the samples on this page.

What is an AMZ scraper?

AMZ is short for Amazon: an AMZ scraper is a tool or API that collects public data from Amazon product and search pages, such as prices, offers, ratings and reviews. ProxyField's Amazon Scraper API does this for $0.60 per 1,000 successful results, from $0.30 at volume.

How can I scrape Amazon for free?

Not at scale: open-source scraper code costs nothing, but IPs cost money. The smallest ProxyField purchase is 1 GB of residential traffic for $2.95, with no minimum purchase and no subscription, on the same pool as a 1 TB order.

How do I get started with an Amazon scraper API?

Contact sales with the pages, marketplaces and daily volume you plan: the price is $0.60 per 1,000 successful results, or $0.30 from 10,000 results in one purchase. Work out your volume first: ASINs × checks per day × 30.

Amazon scraper API: $0.60 per 1,000 results, from $0.30

Billed on successful results only. Contact sales for the API and the volume you need. 24/7 live chat helps with setup and integration.