Amazon Reviews API Guide: Options, Fields, and Limits

Developers searching for an “Amazon reviews API” may mean three different things: an official Amazon insights API, a third-party data-collection API, or a structured export they can ingest. These options have different permissions, fields, and completeness expectations.

Official Customer Feedback API

Amazon's Selling Partner API includes the Customer Feedback API. It exposes review and return insights similar to information available through Product Opportunity Explorer. Access requires an authorized SP-API application, appropriate roles, and a supported marketplace. Its review output is insight- and topic-oriented; it is not a public endpoint that returns every review body for any requested ASIN.

Product Advertising and Creators APIs

Amazon affiliate APIs focus on product advertising content and operate under specific licenses and display requirements. Do not assume an API that returns rating summaries or links also grants unrestricted rights to store or republish full customer reviews.

Third-party collection APIs

Managed providers may accept an ASIN or product URL and return review-like records. Before integrating, evaluate:

• Supported marketplaces and authentication requirements.
• Whether data is live, cached, sampled, or historical.
• Pagination, per-request limits, retries, and rate limits.
• Field definitions, especially posted date versus discovery date.
• Error behavior when a product is unavailable or reviews require login.
• Terms, customer-content rights, retention, and deletion processes.

AMZShark's structured export option

AMZShark does not currently advertise a public REST API. It provides authenticated downloads from product, product-search, and keyword-search pages in CSV, Excel, JSON, JSONL, and Parquet. JSONL and Parquet are especially useful for reliable pipeline handoffs without screen scraping.

Current AMZShark export fields

Exports include ASIN, country code, product title, review URL, rating, AMZShark discovery date, reviewer URL, reviewer name, review title, and review text. They do not currently include verified-purchase, helpful-vote, Vine, media, or exact posted-date columns.

Design an ingestion contract

1. Version your expected schema.
2. Treat missing text and reviewer fields as normal data states.
3. Preserve source URLs and marketplace context.
4. Store the export run time and filter parameters.
5. Make reprocessing idempotent without assuming titles are unique.
6. Alert on unexpected column or type changes.

Choose the least complex suitable option