The Amazon product API is the ASIN-keyed half of Amazon scraping: you hand it a list of product ids and it hands back the detail page as structured data — title, brand, current and list price, star rating, review count, availability, delivery promise, seller, main image, breadcrumb categories and the feature bullets.
It exists because the question "what is on this listing right now" is different from "what does a shopper see when they search". If you already hold ASINs — from your own catalogue, from a supplier feed, or from a run of the Amazon scraper API — this is the endpoint that fills them in. Send up to 50 at a time; each is fetched over the TLS tier without a browser, and any ASIN that never returns a product page comes back under failed rather than as a row of invented nulls.
$0.003 per delivered product, up to 50 products per run. Nothing delivered means nothing charged.
You post an array. Every entry can be a bare ASIN or a full /dp/ URL — the collector normalises both, so you can feed it whatever your pipeline already stores without a cleanup step first.
Each ASIN becomes one product-page fetch through a residential exit in the country you asked for, parsed into a flat row. Three behaviours are worth knowing before you wire it in:
failed. It is not billed and it does not appear as a half-empty row that quietly poisons an average price later.The only required input is asins, an array. max_results caps how many of them the run will actually fetch, which is a cheap safety belt when the array is built by another job — you can pass 200 ids and spend on 50. country selects the marketplace and the matching proxy exit.
Every product is one flat row. price is what the page displays and price_value is the number behind it, so you can diff without parsing currency symbols. list_price is only present when Amazon is showing a struck-through price, which makes it a reliable discount signal rather than something you infer. categories carries the breadcrumb path and features the bullet list — the two fields people most often reach for when building a product catalogue rather than a price tracker.
$0.003 per delivered product ($3 per 1,000). Nothing delivered means nothing charged, and the $2 monthly free credit covers roughly 666 products here. Volume tiers take up to 30% off.
$0.003 per delivered product, $3 per 1,000. A 5,000-ASIN catalogue refreshed daily is $15 a day at list price, less on a volume tier. The pattern that keeps that bill down is not a discount, it is the split: use the cheaper search collector at $0.001 for discovery over a wide keyword set, and spend $0.003 only on the ASINs you decided are worth watching.
ASINs that fail to resolve are not billed, so an ageing id list degrades your coverage rather than your invoice.
Amazon's own Product Advertising API returns catalogue attributes for items you name — which sounds like exactly this. The difference is who is allowed to call it. PA-API is part of the Associates affiliate programme: you need an approved Associates account, and access is metered against qualifying sales, so an account that stops converting can lose throughput or access entirely. Teams doing price intelligence, brand protection or academic research usually do not have and do not want an affiliate relationship.
There is also a content gap. PA-API returns the catalogue's view of an item. This collector returns the page — the delivery promise as shown, the availability line, the seller currently winning the listing, the struck-through list price. Those are rendering decisions Amazon makes per visitor and per country, and they are what most price-monitoring work is actually about.
Fetching one product page is trivial. Fetching fifty thousand without getting throttled is the whole engineering problem, and it has a shape people underestimate:
Handing that over buys you a published schema and a bill that only moves when rows arrive. If you would rather keep the fetcher and just want clean exits under it, our residential proxies are the network this runs on.
Refresh a watchlist every morning and diff price_value, list_price and seller. A seller change on a listing you own is usually the alert that matters more than the price itself.
The availability and delivery lines are the page's own words. Watching them beats inferring stock from whether the page loaded.
Feed supplier ASINs in, get categories, features, brand and images out — enough to populate an internal product record without anyone copy-pasting a listing.
Track who is selling your ASINs and at what price across marketplaces by running the same id list with a different country.
One run takes up to 50 ASINs. Larger id lists are simply more runs — there is no session to keep alive between them, so they parallelise cleanly up to your plan's rate limit (60 requests/minute on pay-as-you-go, up to 1,200 on the top tier). Unresolvable ASINs return in failed with no charge.
Legally: listing data is published publicly and collecting public data is generally lawful in most jurisdictions, but Amazon's terms restrict automated access, the analysis varies by country, and what you do with the data afterwards matters as much as how you got it. This is not legal advice — get some for your actual use case.
There is a free monthly allowance rather than a free tier you stay on forever: $2 of usage every month with no card, which at $0.003 per product is about 666 delivered products. Amazon's own Product Advertising API is free to call but requires an approved Associates affiliate account, which is a different kind of cost.
No. You authenticate with your QuantumProxies API key and nothing else. There is no Amazon developer registration, no Associates approval and no per-marketplace credential to maintain.
$0.003 per delivered product — $3 per 1,000 — with no subscription. ASINs that never resolve are returned under failed and are not billed. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.
Yes. The asins array accepts bare ASINs or full /dp/ product URLs and normalises them, so you can pass whatever your database already holds without writing a cleanup step.
You do not, and no API does — Amazon does not publish a full catalogue dump. The workable pattern is discovery plus enrichment: run the Amazon scraper API over the keyword set for your category to collect ASINs, then push the ones you care about through this collector for detail.
Up to 50 per run. Bigger lists are just more runs, and because each run is independent they parallelise up to your plan's requests-per-minute limit rather than queueing behind one another.
No. It returns the rating and the review count from the detail page, which is what ranking and quality work needs. Individual review text is a separate job with its own volume and privacy considerations.
Skip the marketing. QuantumProxies.io publishes a machine-readable site map, Markdown for every page, a free MCP server, and APIs billed from the same balance as your proxies.
Connect in one command: npx -y quantumproxies-mcp