What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Short answer: Amazon’s current official route is the Creators API. It can return catalog fields, images, offers and variation data, and its SearchItems operation can filter products by review rating. The documented API does not establish general access to full customer-review text or a complete review archive. If you need review bodies, you must first establish a permitted data source and usage rights; do not assume that a rating filter is a reviews API.

What Amazon’s official API provides

Amazon describes Creators API as a REST API for programmatic access to product-catalog data for publishers, influencers and affiliate partners. Its documented operations are:

  • SearchItems: search products by keywords and other search fields.
  • GetItems: retrieve item attributes, offer listings, images and related resources.
  • GetVariations: retrieve variation information for a product.
  • GetBrowseNodes: look up browse-node information.

The API reference and ItemInfo resource describe titles, brands, descriptions, features, technical information, classifications and external identifiers. Availability varies by marketplace, locale, category and ASIN, so design your importer to tolerate missing fields rather than assuming every item has the same schema.

SearchItems returns up to ten items per request. It supports resources such as ItemInfo, Images, OffersV2 and search refinements. The SearchItems reference also lists minReviewsRating, a filter for products whose customer-review rating is above a specified value. That filter is evidence of rating-based selection, not permission or capability to download arbitrary review bodies.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Can you get Amazon reviews through an API?

Not as a general review-text feed through the documented Creators API. You can use the rating filter while searching, and catalog responses may include rating-related information where the selected resource and marketplace provide it. The reviewed documentation does not promise the full text of customer reviews, reviewer identities, timestamps for every review, pagination through a review archive, or sentiment-analysis-ready exports.

Amazon Business has a separate Product Search API documentation page that identifies customerReviewsSummary as a privileged field. Amazon reviews eligibility for requested privileged fields; this is not documentation of unrestricted review-text retrieval. The Amazon Ads API concerns advertising campaign management and reporting, not product-review extraction.

Access requirements before you write code

Amazon’s current Creators API overview lists these prerequisites for the relevant access path:

  1. Enrollment in Amazon Associates for the target marketplace.
  2. At least 10 qualifying sales in the previous 30 days to access the PA API through Creators API.
  3. Registration for API access.
  4. Generated API credentials.

These conditions are stated on the live onboarding page and may change. Confirm eligibility for the marketplace you will query before committing to an integration. Credentials are marketplace- and account-sensitive; never put them in browser JavaScript, a public repository or a client-side application.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The old PA-API documentation labels itself outdated, points readers to Creators API and lists a May 15, 2026 deprecation date: legacy PA-API documentation. As of September 2026, use Creators API documentation for a new project. The cited material does not establish identical shutdown behavior for every legacy account or endpoint, so do not build a new system around PA-API merely because an old example still works.

Policy boundaries for catalog and review collection

Amazon’s Associates operating policies state that the Associates license does not include data mining, robots or similar data-gathering and extraction tools. The policy also restricts displaying or otherwise using customer reviews or star ratings, in whole or in part, unless a link to that review or rating was obtained through Creators API or PA API and the applicable requirements are followed.

That is a policy statement for the Associates license, not a universal legal conclusion about every automated request, public webpage or jurisdiction. If your project is outside Associates, involves storing review text, or will be used commercially, obtain advice specific to your country, data sources and intended use. Rate-limit requests, identify your application where required, and retain only fields your approved use permits.

A practical catalog-data workflow

1. Define the fields and marketplace

Choose the target marketplace, language and fields before requesting data. A useful normalized record might contain ASIN, title, brand, product URL, images, identifiers, category, variation relationship, price/offer fields, and the rating value when supplied. Mark absent values as null and preserve the source marketplace.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

2. Request only the resources you need

Creators API resources determine which groups of fields are returned. Requesting ItemInfo, Images and OffersV2 for every item increases response size and processing cost compared with requesting only ItemInfo for a discovery pass. Use SearchItems for discovery, then GetItems for details on the ASINs you actually retain.

3. Use rating filters correctly

Apply minReviewsRating as a product-selection criterion, for example “products rated at least four stars,” not as a substitute for review retrieval. Record the query, marketplace, date and filter value so downstream users understand what the result means.

4. Handle pagination and limits explicitly

SearchItems returns no more than ten items per request according to its reference. Follow the operation’s documented pagination fields and stop conditions; do not assume that repeatedly changing a page number will expose an unlimited result set. Persist the request parameters and continuation token with each batch for reproducibility.

5. Cache and refresh deliberately

Catalog attributes and offers change at different rates. Cache stable identifiers and descriptive fields longer than prices or availability, and attach a fetched-at timestamp to every record. Never treat a cached rating or offer as real-time unless your refresh schedule supports that claim.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Python request pattern

Amazon’s credential signing and endpoint details vary by the current Creators API documentation and marketplace. The following pattern keeps the endpoint and authentication configuration outside source code; fill those values from your approved account’s live documentation rather than copying a retired PA-API example.

import os
import requests

API_URL = os.environ["CREATORS_API_SEARCH_URL"]
ACCESS_TOKEN = os.environ["CREATORS_API_ACCESS_TOKEN"]

payload = {
    "Keywords": "wireless headphones",
    "SearchIndex": "All",
    "ItemCount": 10,
    "Resources": ["ItemInfo", "Images", "OffersV2"],
    "MinReviewsRating": 4
}

headers = {
    "Authorization": f"Bearer {ACCESS_TOKEN}",
    "Content-Type": "application/json",
    "Accept": "application/json"
}

response = requests.post(API_URL, json=payload, headers=headers, timeout=30)
response.raise_for_status()
data = response.json()
for item in data.get("Items", []):
    info = item.get("ItemInfo", {})
    print(item.get("ASIN"), info.get("Title"))

Use the exact field casing, signing scheme, HTTP method and authorization headers shown in the current Creators API reference for your account. The example demonstrates validation, timeouts and defensive extraction; it does not claim that a Bearer token is the only supported authentication method.

Equivalent cURL and Node.js patterns

curl -X POST "$CREATORS_API_SEARCH_URL" 
  -H "Authorization: Bearer $CREATORS_API_ACCESS_TOKEN" 
  -H "Content-Type: application/json" 
  -d '{"Keywords":"wireless headphones","SearchIndex":"All","ItemCount":10,"Resources":["ItemInfo","Images","OffersV2"],"MinReviewsRating":4}'
const url = process.env.CREATORS_API_SEARCH_URL;
const token = process.env.CREATORS_API_ACCESS_TOKEN;
const response = await fetch(url, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${token}`,
    'Content-Type': 'application/json',
    Accept: 'application/json'
  },
  body: JSON.stringify({
    Keywords: 'wireless headphones',
    SearchIndex: 'All',
    ItemCount: 10,
    Resources: ['ItemInfo', 'Images', 'OffersV2'],
    MinReviewsRating: 4
  })
});
if (!response.ok) throw new Error(`${response.status} ${await response.text()}`);
const data = await response.json();
for (const item of data.Items ?? []) console.log(item.ASIN, item.ItemInfo?.Title);

See Amazon’s Creators API onboarding and reference for the authoritative endpoint, resource names and authentication requirements.

What to do when you specifically need review text

  • Do not infer review-body access from minReviewsRating.
  • Check whether your approved Amazon program exposes a permitted review-summary field; Amazon Business’s privileged-field process is separate.
  • If you are evaluating public-page collection, treat the Associates policy restrictions as a gating issue and obtain jurisdiction-specific advice before collecting or redistributing text.
  • Design your schema so a missing review body is a normal state, not an API failure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Troubleshooting common failures

401 or 403 responses

Usually the credential, marketplace, authorization header or account eligibility is wrong. Recheck registration and the current onboarding requirements; do not switch to an old PA-API signing example without verifying that it is still supported.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Empty fields

Field availability varies by locale and category. Confirm that the required resource was requested and handle absent ItemInfo members without crashing.

Fewer than ten results

Ten is a maximum, not a guarantee. Keywords, category, marketplace and filters can reduce the result set.

No review bodies

This is expected for the documented catalog scope. A rating filter selects products; it does not return an archive of customer comments.

Rate limits or intermittent errors

Use bounded retries with exponential backoff for transient 5xx responses, respect Amazon’s published limits, and log request IDs without logging secrets. Avoid concurrent bursts that your account has not been approved to make.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Or skip the browser setup

If your real goal is to capture how an Amazon product page renders—not to obtain review data—ScreenshotNeo can return a screenshot or PDF with one request. It accepts cookie and consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.

For a product URL, use the documented API examples at ScreenshotNeo’s docs:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Replace the URL with the page you are authorized to capture. ScreenshotNeo includes 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 shots. Every feature is on every plan. Create a free ScreenshotNeo account.

Cost, reliability and data-quality checklist

  • Verify Associates eligibility and marketplace coverage before estimating volume.
  • Store the request parameters, marketplace, response timestamp and ASIN.
  • Separate immutable identifiers from volatile offer and rating fields.
  • Use retries only for transient failures and preserve error responses for diagnosis.
  • Never represent a rating filter as review-text access.
  • Review Amazon’s current terms whenever your data use, geography or account status changes.

Frequently Asked Questions

Does Creators API return every product field for every ASIN?

No. Amazon states that field availability varies by locale and product category, so clients must handle missing resources and attributes.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Is Amazon Business’s customerReviewsSummary a public review API?

No. It is documented as a privileged field subject to Amazon’s eligibility review; the cited page does not establish unrestricted full-text access.

Should a new project still use PA-API?

Use the current Creators API documentation for new work. Amazon’s legacy PA-API page is marked outdated, points to Creators API and lists May 15, 2026 as its deprecation date.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.