Home / Amazon Price Monitoring & Price History
Amazon Price Monitoring & Price History
What changed when PA-API was deprecated, which routes still work, and why the page price is often the wrong product.
Amazon price monitoring means tracking price, buy-box ownership and availability for ASINs over time. Since PA-API 5.0 was deprecated on 15 May 2026, the practical routes are the Creators API (which requires ongoing affiliate sales) or a third-party product API. Direct scraping succeeds roughly 2% of the time.
What changed in 2026
For a decade the answer to “how do I get Amazon prices” was the Product Advertising API. That ended on 15 May 2026, when PA-API 5.0 was deprecated. Its successor, the Creators API, is gated behind affiliate performance: you need 10 qualifying sales in a rolling 30-day window to hold credentials, and access is withdrawn when you fall below it.
That gate is fine for a content publisher and unworkable for a data product. A monitoring system cannot have its credentials revoked because last month's referral traffic was soft. It is the single most important fact about Amazon data in 2026, and most articles on the subject have not caught up with it.
The four ways to get Amazon pricing, honestly compared
| Route | Cost | Reliability | Catch |
|---|---|---|---|
| Creators API | Free | Conditional | Revoked below 10 qualifying sales / 30 days |
| Third-party product API | $0.002–0.012 / request | High | You inherit the vendor's terms and coverage |
| Direct scraping | Infrastructure + time | ~2% success | Six-layer request scoring; see below |
| Selling Partner API | Free | High, narrow | Only your own listings, not competitors' |
The Selling Partner API is worth calling out because it gets confused with the others: it is excellent for your own catalogue and useless for competitive monitoring, since it cannot see listings you do not own.
Why scraping Amazon does not scale
Amazon scores every inbound request for how likely it is to be human, across roughly six signal layers — TLS fingerprint, HTTP/2 frame ordering, header entropy, IP reputation, behavioural timing and browser attestation. A conventional script behind rotating datacentre proxies succeeds at roughly a 2% rate. We measured this directly: 25 request variants across five user-agent profiles from a clean residential address returned no usable product page.
The failure mode that matters is not the block, it is the silent one. Defended retailers serve deliberately altered prices to traffic they classify as automated. A monitoring system on datacentre addresses can report fabricated competitor prices with complete confidence, and its operator has no way to detect it.
Buy box: the price belongs to a seller, not a product
On Amazon the entity that carries a price is the offer, not the product. Many sellers list the same ASIN, and the one holding the buy box at any moment owns the displayed price. Ownership recalculates continuously from price, shipping, fulfilment method and seller metrics.
Recording a price without recording who was selling it destroys the meaning of the observation. A drop from $319 to $198 is a promotion if Amazon itself holds the box and a channel problem if an unfamiliar reseller took it. Buy-box changes also tend to precede the price move that makes them obvious, which makes them the earlier signal of the two.
ASINs do not travel
An ASIN is Amazon's internal identifier. It is not a GTIN, it has no meaning at Walmart or Best Buy, and it cannot be used to join across retailers. Cross-retailer comparison requires resolving the ASIN to a real product identity — a GTIN where one is published, brand and normalised title where it is not.
This is where most comparison projects quietly break. Two listings that look identical in a spreadsheet can be a 12-pack and a 24-pack, or last year's model and this year's. We return a match method and a confidence on every mapping for exactly this reason, and flag anything below the trust threshold rather than accepting it silently.
Price history cannot be backfilled
Every other component of a monitoring system can be built in a quarter. History cannot be built at all — it only accumulates forward. A team starting today has ninety days of history in ninety days, and there is no shortcut, which is why it is the one genuinely defensible asset in this category.
It is also why a percentile against a product's own history is a more honest measure of a discount than percent-off a reference price. The reference price is chosen by the seller; the history is not.
GET /v1/products/0885909950805/context?seller=amazon&days=90
{ "verdict": "excellent",
"current": "$198.00",
"compared_against": "amazon", // its own history, never pooled
"percentile": 4.0,
"covered_days": 89,
"low": "$198.00", "median": "$319.99", "high": "$398.00" }What we actually measured
- Amazon's search grid returns 28 priced ASINs in a single response before scrolling, against 58 tiles carrying a data-asin attribute — so grid reads are roughly 28× cheaper per product than detail-page reads.
- The same Sony WH-1000XM5 read $198.00 at both Amazon and Best Buy on 7 September 2026 — a genuine cross-retailer match, resolved by GTIN rather than by title similarity.
- Third-party product APIs price between $0.002 and $0.012 per request depending on tier and field coverage.
Variations, and the price that is not the price
An Amazon product page is frequently a variation family — sizes, colours, counts, flavours — sharing one page, one review set and one apparent identity, while each child is a separate ASIN with its own price, availability and buy box. The price a page appears to show is whichever child was selected by default, and that default can change. A tracker recording 'the price of this page' is recording the price of a child it did not choose and cannot name.
This is the most common quiet failure in Amazon price tracking, and it produces a series that looks entirely plausible: prices move, the chart has shape, nothing errors. What actually happened is that the default child changed from the 12-count to the 3-count, and the 60% 'price drop' is a different product. Track child ASINs individually and record which parent they belong to rather than collapsing them.
| What you see | What it actually is | What to record |
|---|---|---|
| The page price | The default child's price | The child ASIN's own price |
| A price drop | Sometimes a different default child | Child ASIN on every observation |
| One review score | Shared across the whole family | Family-level, not per child |
| 'In stock' | The selected child's state | Availability per child ASIN |
Coupons, subscriptions and promotional structure
A substantial share of Amazon's effective discounting never touches the listed price. Clippable coupons apply at checkout, subscription discounts apply to a different purchase mode, and quantity offers change unit economics without changing the unit price. A series recording only the listed figure is accurate and systematically overstates what buyers paid during promotional periods.
The honest treatment is to record what is observable, label it for what it is, and be explicit that promotional structure sits outside the series rather than quietly folding an estimate into it. A tool reporting a single 'real price' by guessing at coupon applicability has converted a measurement into an assumption without telling anyone.
Reference prices and what percent-off actually means
A struck-through comparison price is a seller-chosen reference, not an observed prior transaction price, so percent-off that reference is a claim rather than a measurement. This matters because it is the number most price tools surface most prominently — and it can be large while the actual price sits at the top of the product's own recent range.
Percentile against the product's own observed history is the defensible measure. It answers a question with a checkable answer — where does today sit against what this item has actually cost — rather than repeating a comparison the seller chose. The two frequently disagree, and when they do, the percentile is the one grounded in evidence.
Third-party sellers change what you are measuring
A large share of units on Amazon are sold by third-party merchants rather than by Amazon itself, and their offers are not interchangeable. Fulfilment differs, return handling differs, seller reliability differs. Recording an offer without recording who is making it produces a series that silently mixes first-party and marketplace offers — and for MAP enforcement or brand protection, seller identity is frequently the entire point rather than metadata.
- Seller identity belongs on every observation, not on the product.
- A seller flip is a material event even when the price does not change — different fulfilment, returns and risk.
- Unauthorised sellers are identified by who they are, not by what they charge, so price alone cannot detect them.
- Offer count is a signal in its own right: a listing going from twelve offers to two is telling you something about supply.
Questions
Common questions
Is there a free Amazon price API?
The Creators API is free but conditional — it requires 10 qualifying affiliate sales per rolling 30 days, and credentials are withdrawn below that threshold. For anything that needs to keep running regardless of referral performance, a paid third-party API is the realistic route.
Is scraping Amazon prices legal?
Courts in the United States have held that accessing publicly available data is not unauthorised access under the Computer Fraud and Abuse Act. Terms of service are a separate question and are contractual rather than criminal. The practical constraint is different again: it succeeds around 2% of the time at scale, so legality is rarely the binding limit.
How far back does Amazon price history go?
It depends entirely on when collection started for that ASIN, because history cannot be reconstructed retroactively. Any provider claiming deep history on a product they only began tracking recently is describing something they cannot have.
Can I track the buy-box seller as well as the price?
Yes, and you should. Seller identity rides on every observation, so a price change attributable to a new reseller taking the buy box is distinguishable from Amazon itself discounting.
What is the difference between the Selling Partner API and a product API?
The Selling Partner API exposes your own listings and is the right tool for managing them. It cannot see competitors' listings, which is what monitoring requires.
Related
Walmart Price Monitoring & Product Data
How to get Walmart pricing data: the affiliate API route, why prices are stripped from the page payload, and how marketplace sellers change the picture.
MAP Monitoring & Minimum Advertised Price Enforcement
How MAP monitoring works: detecting violations across marketplaces, identifying unauthorised sellers, and building evidence that survives a lawyer reading it.
Price History API
How price history should be stored and read: append-only observations, time-weighted percentiles, why ties need midrank, and why history cannot be backfilled.