Ecommerce Scraper API - Amazon, Walmart, Google Shopping

Turn keywords, ASINs and product IDs into clean ecommerce rows: prices, sellers, ratings and rankings from Amazon, Walmart, Target, Best Buy, Etsy and Google Shopping, parsed and ready for a spreadsheet.

What it collects

• Amazon search results: organic, sponsored, suggested and Amazon's Choice items for any keyword on 23 Amazon marketplaces, with ASIN, title, brand, price, rating, review count, Prime and best seller flags, position and shipping text. Filter by category node, seller, price range and Amazon's own refinements, and sort by price, reviews, newest or best sellers.
• Amazon product pages: one product by ASIN with its buy box, price, seller, stock, delivery options, bullet points, category ladder, ratings and the rest of the provider's parsed page.
• Amazon offer listings: every seller offer for an ASIN, one row per offer, with price, shipping price, condition, seller name and ID, seller rating and delivery options. The row you want for buy box and repricing work.
• Amazon best sellers: the ranked best seller list for any browse node, with position, ASIN, title, price and ratings.
• Walmart: search results with price, strikethrough price, rating, seller, sponsored flag and fulfillment options, filtered by price, sort, fulfillment type and speed, store or delivery ZIP; and product pages by product ID with GTIN, SKU, specifications, variations and seller.
• Target: search results with brand, price, rating and shipping message; and product pages by product ID, localised by store, fulfillment type or delivery ZIP.
• Best Buy and Etsy: product pages by product or listing ID with price, rating, seller and availability.
• Google Shopping: search results across merchants (organic listings and product listing ads) with price, merchant, rating, delivery and a product token; and product pages by token with every online store's price, reviews, variants and specifications.

How to use it

1. Pick a source under What to read.
2. Add one keyword or identifier per line: a keyword for search, an ASIN for Amazon product and offer pages, a browse node ID for best sellers, a product ID for Walmart, Target, Best Buy or Etsy, or a Google Shopping product token.
3. Optionally set the marketplace domain, a delivery location, filters, sort order and how many pages to read.
4. Paste your own API username and password, and run.

Filters that the chosen source does not document are left off with a warning in the log rather than sent, so a run never looks filtered when it was not.

Example output

{
  "service": "amazonSearch",
  "serviceLabel": "Amazon search results",
  "source": "amazon_search",
  "requested": "wireless earbuds",
  "page": 1,
  "section": "organic",
  "found": true,
  "recordType": "listing",
  "productId": "B0DHVH5KCB",
  "title": "Open Ear Earbuds 40H Bluetooth 5.4 Lightweight Comfort",
  "price": 26.98,
  "currency": "USD",
  "rating": 4.3,
  "reviewsCount": 45795,
  "seller": null,
  "position": 1,
  "url": "/dp/B0DHVH5KCB",
  "parseStatus": 12000,
  "retrievedAt": "2026-09-25T10:14:52.118Z",
  "record": { "...": "every field the provider parsed, unchanged" },
  "note": null
}

FAQ

What is an ecommerce scraper API used for?

Price monitoring, competitor tracking, marketplace research and catalogue enrichment. A brand watches its own and rival listings on Amazon, Walmart and Target every day. A reseller reads every seller offer on an ASIN to see who holds the buy box and at what price. A category manager pulls the Amazon best seller list for a browse node each week. A comparison site reads Google Shopping to see every merchant's price for one product. The shape is always the same: a list of keywords or IDs in, a table of products and prices out.

Do I need an API key?

Yes. This actor is bring-your-own-key: it calls a realtime web scraping API with your own account's API username and password and never ships credentials of its own. Paste both into the input, paste username:password into the password field, or set them once as the DATA_API_USERNAME and DATA_API_KEY environment secrets. They travel as an HTTP Basic authorization header, never in a URL. A missing or refused credential ends the run cleanly with a message saying what to fix, rather than failing it.

What does it cost?

Two things are billed separately. This actor charges per result row: a search, best seller or offer row costs less than a full product page, because one search page returns dozens of rows. Your scraping API provider bills your own account per job under your plan; each results page is one job. Rows for keywords that returned nothing, products that were not found and pages the provider could not parse are never charged here.

Which Amazon marketplaces are supported?

The ones the provider documents: com, ca, co.uk, de, fr, it, es, nl, pl, se, ie, com.be, com.tr, ae, sa, eg, in, co.jp, cn, sg, com.au, com.br and com.mx. Set the delivery location with a ZIP or postal code inside the marketplace country, or a 2-letter country code for delivery abroad, because Amazon changes prices and availability by delivery address.

How do I get Google Shopping product prices from every store?

Run the Google Shopping search source first. Each row carries a token in its record. Paste those tokens into a second run on the Google Shopping product source to read each product's page with every online store's price, and turn on JavaScript rendering to include the More stores section.

Why is the full record kept as well as the columns?

Because every retailer's page parses into a different shape, and a fixed set of columns would drop most of it. The lifted columns (identifier, title, price, currency, rating, review count, seller, position, URL) are the ones the provider names across sources. Everything else it parsed sits under record, unchanged.

Can this actor buy anything or send data elsewhere?

No. The only route it calls submits a job that reads a public page and returns it parsed. It never sends a callback URL or a cloud storage target, so results come back to this run only. The Amazon seller profile source is deliberately not wired, because its answer carries seller email addresses, phone numbers and reviewer names.

What does a parser status mean on a row?

The provider grades each parsed page. 12000 is a full parse. 12004 and 12005 are partial parses, which are kept and marked with a note. Failures such as 12002 (layout changed), 12003 (page not supported) and 12009 (product not found) become a found: false row with the reason, and are not charged.

Keyword map

ecommerce scraper API, Amazon scraper API, Amazon product data API, Amazon search results scraper, Amazon ASIN lookup, Amazon offer listing scraper, Amazon buy box data, Amazon best sellers scraper, Amazon price tracker, Walmart scraper API, Walmart product data, Target scraper API, Best Buy product scraper, Etsy product scraper, Google Shopping scraper API, Google Shopping prices, price monitoring API, competitor price tracking, product data extraction, ecommerce data API, marketplace data scraper, web scraper API bring your own key.