Hand over a list of ASINs or product URLs and get the listing behind each one back as a row - title, price, rating and review count. Seventeen Amazon marketplaces, one export. No proxies, no parsers, no code.
Amazon publishes product detail in the page itself rather than through a public feed, so the practical input is the identifier you already hold: the ASIN, or the product URL.
One row per product. The pre-flight estimator shows the product count and credit cost before the run starts.
A supplier sheet, a competitor list, a category export - if it has ASINs or product URLs in a column, it's already a valid input.
The same ASIN can carry a different price and currency in every region. Pull them side by side instead of opening seventeen tabs.
CSV and XLSX for a spreadsheet, or call the API and pipe results straight into your own pricing or merchandising system.
Each row carries the product detail Amazon shows on the page: the product name and its ASIN, the current price and currency, any badge on the listing, the star rating and review count, the product URL, and - where Amazon publishes them - dimensions and active coupons.
Because the exact column set varies by category (a book carries author and publication detail that a power tool does not), we deliberately don't publish a fixed column list here that would be wrong for half of Amazon. Run a small job on the free tier first and the header row will tell you precisely what your categories return.
The header row is enormous - 132 columns - but most of it is category-specific and empty for any given product. These are the ones that actually carry data.
$788.49.USD or INR.old_price, at 27%.Two things worth knowing before you build. First, availability and shipping exist as columns but arrived on only 1.6% of 244 rows - do not plan a stock workflow around them. Second, the export carries roughly 110 further details_* and overview_* columns that are specific to a product category - horsepower and incline for a treadmill, compatible phone models for a case - so they are present for the products that have them and empty for everything else. Read them opportunistically rather than expecting a fixed set. Prices come in both display and parsed form, which saves stripping currency symbols yourself.
Every regional storefront we support, by domain. The same ASIN can be priced and stocked differently in each one.
A few examples of how teams use Amazon product data.
Feed in the ASINs you compete against and re-run on whatever cadence your category moves at. Price per row means you can see undercutting rather than inferring them.
Run the same ASIN list against several marketplaces. Where the price gap differs sharply, you have a concrete case for a regional listing change - backed by the live pages, not a guess.
Export your full ASIN range and diff it against your source of truth. Wrong titles, missing descriptions, stale prices and lost badges surface in a spreadsheet instead of a customer complaint.
No subscription, no minimum. Your first 500 products are on us - after that, pay-as-you-go, and the rate drops at volume.
Every new account, one-time. No credit card required. CSV / XLSX export, filters and API access included.
That's $2 per 1,000 products above the free tier. The pre-flight estimator shows row count and credit cost before a run starts - no surprises, no compute units to translate.
For very large or continuous catalogue pulls, talk to us about volume pricing, dedicated workers and an SLA.
LIVESCRAPER10 at checkout.Teams working a product category usually run one of these alongside.
Returns a shopping block per query - title, link, price and merchant - so you can see who else is selling a product and at what price outside Amazon.
Sourcing rather than monitoring? Point this at a list of supplier or brand domains to pull the emails, phones and socials behind them.
Short answer: yes for the public listing data - and that is all we ever collect.
A product page is public: Amazon shows the title, price, availability and rating to anyone, signed in or not. Collecting publicly visible facts about a product for price comparison and market research is long-established practice, and as long as the data is publicly available and the process doesn't disrupt the site there are no federal laws prohibiting it.
Worth being straight about the commercial side: Amazon's terms of service restrict automated access, so this is a terms question as much as a legal one. We handle no logins and touch nothing behind an account. If you have a contractual relationship with Amazon, check it - that's your call to make, not ours to make for you.
We collect no personal data, run no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
500 one-time free products on every new account - no expiry. After that it's $0.002 per product, pay-as-you-go - no card on file until you say so.
Livescraper's Amazon Products Scraper turns a list of identifiers into structured product data. You submit ASINs or product page URLs, set a limit per page, and download the listing behind each one as a clean CSV or Excel file - or call the API and skip the download entirely.
Each row carries the product detail Amazon publishes on the page: the product name, the ASIN, the current price and its currency, any badge on the listing, the star rating and review count, and the product URL. Categories that publish more - dimensions, coupons, publication detail on books - return more, which is why the header row of a small test run is the most reliable column reference for your own catalogue.
Pricing teams use it to watch competitor ASINs on whatever cadence their category moves at. International teams run one ASIN list against several of the seventeen supported marketplaces to see where price and currency diverge. Operations teams export their own range and diff it against their source of truth to catch stale prices and missing copy before a customer does.
Amazon publishes product detail in the page rather than through a public feed, so there is no free API to call - which is precisely the gap this fills. Start free: your first 500 products cost nothing and need no credit card, and the rate halves past five thousand.