Developers who search for an "Amazon reviews API" usually want one thing: pass an ASIN, get the review text back as JSON.
None of Amazon's own APIs does that for an arbitrary product. They return things about reviews — counts, ratings, summarised topics — and each is limited to a particular kind of account. Knowing which is which saves a week of reading documentation for a field that is not there.
What each official API returns about reviews
| API | Who it is for | What it returns about reviews | Review text of any ASIN |
|---|---|---|---|
| Selling Partner API | Sellers and vendors, for their own account | Orders, listings, reports. Its Customer Feedback API adds summarised review topics, not individual reviews | No |
| Affiliate API (Product Advertising API and its successor, the Creators API) | Associates and creators building product links | Catalog data for linking, including rating information | No |
| Amazon Ads API | Advertisers, for their own campaigns | Campaign management and reports | No |
Three notes on that table.
The Customer Feedback API is the closest, and it is a summary. Amazon's documentation describes it as insights from customer reviews and returns, at the ASIN and browse-node level: the most positive and most negative topics. It is an analysis Amazon has already done, not the reviews themselves, and access needs approval.
The affiliate API exists to build links. It is meant for sites that send shoppers to Amazon. Amazon's documentation now names the Creators API as the supported successor to Product Advertising API 5.0, so check the current terms before building on either.
Scope is the real limit. The seller and advertising APIs are about your own account. A competitor's reviews are outside them by design, not by missing permission. The same split applies to every other kind of data, as choosing an Amazon data API explains.
What a review-text request looks like
A third-party data endpoint fills the gap. This one takes an ASIN and returns its reviews page by page:
curl --request POST \
--url https://ecommercedataapi.com/v1/amazon/review \
--header "Content-Type: application/json" \
--header "X-API-Key: ${ECOMMERCE_DATA_API_KEY}" \
--data '{
"marketplace": "US",
"asin": "B08CK5Z5Q1",
"page": 1,
"size": 20,
"stars": [1, 2, 3]
}'Each item in items[] is one review:
| Field | What it tells you |
|---|---|
star, title, content | Star rating and the review text |
date | Review date, as a millisecond timestamp |
skus | The variation the reviewer bought |
likes | How many shoppers marked it helpful |
verified, vine, free, experience | Where the review came from |
image, video, images, videos | Whether it has media, and the links |
stars filters by rating, so [1, 2, 3] returns only the critical reviews. The response carries total and pages for paging.
The Amazon Reviews API page lists the marketplaces and the common workflows.
Four things to handle in code
1. date is a timestamp, not a string. Convert it before grouping by month. Storing it lets you compare reviews before and after a product change.
2. skus is how you split by variation. A parent listing pools reviews from all its variations. Group on skus before concluding that "the product" has a problem; often one size or color does. Parent and child ASINs covers what is pooled and what is not.
3. Keep the four sources apart. A Vine review and a verified purchase are different evidence. Count them separately, for the reasons in the four sources of an Amazon review.
4. Page deliberately. Each successful call uses one billing unit. For a product with thousands of reviews, decide first whether you need all of them or only the critical ones from the last few months.
What review data cannot do
It is a sample of people who chose to write. Rare complaints look larger than they are. Read counts next to likes and dates.
It shows a problem, not its cause. Fifty reviews saying "stopped working" do not tell you which part failed.
It is not a basis for product claims. Customer opinion is not test evidence.
What to do with the reviews once you have them is in how to analyse Amazon reviews, and the spreadsheet route is in exporting reviews into a spreadsheet. Splitting critical reviews by variation and by theme is in reading negative reviews by variation.
Questions
Does Amazon have an official reviews API? Not one that returns the review text of any product. The Selling Partner API offers summarised review topics for approved developers; the affiliate API offers rating information for building links.
Can I get only negative reviews?
Yes. Pass "stars": [1, 2] or [1, 2, 3].
Can I get reviews for a competitor's product? Yes. The endpoint takes any ASIN in the supported marketplaces.
Can an AI agent read the reviews for me? Yes. The same endpoint is a tool on the remote MCP server, so an agent can fetch reviews and summarise them in one conversation.