Discover/Amazon API
live

Amazon APIamazon.com ↗

Access Amazon product data via 8 endpoints: search by keyword, get product details, reviews, seller offers, best sellers, deals, and cart management.

Endpoint health
verified 1d ago
search_products
get_product_reviews
get_cart
get_deals
get_best_sellers
7/7 passing latest checkself-healing
Endpoints
8
Updated
1mo ago

What is the Amazon API?

The Amazon API covers 8 endpoints that expose product search, detail pages, customer reviews, seller offers, best-seller rankings, and live deals. The search_products endpoint accepts a keyword query and returns paginated results including ASIN, price, rating, review count, and a "bought in past month" sales figure. Full product detail pages are available through get_product_details, returning structured specifications, bullet-point descriptions, and per-star rating breakdowns.

This call costs10 credits / call— charged only on success
Try it
Page number for pagination (1-based).
Sort order for results.
Filter results by brand name (e.g. 'Schylling', 'Anker'). Case-sensitive as passed to Amazon's refinement filter.
Search keyword (e.g. 'usb cable', 'laptop').
Amazon department/category code passed as the 'i' parameter (e.g. 'electronics', 'books').
When true, filters results to only products sold by Amazon.com (excludes third-party marketplace sellers).
→ api.parse.bot/scraper/e1dc349c-16b6-498a-a7e6-2462aef5b5b4/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/e1dc349c-16b6-498a-a7e6-2462aef5b5b4/search_products?page=1&sort=price-asc-rank&brand=Schylling&query=usb+cable&category=electronics&sold_by_amazon=true' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 8 totalmissing one? ·

Search for products on Amazon by keyword. Returns paginated results with product title, price, rating, and image. Supports optional category filtering, sort order, brand filtering, and filtering to only Amazon-sold items.

Input
ParamTypeDescription
pageintegerPage number for pagination (1-based).
sortstringSort order for results.
brandstringFilter results by brand name (e.g. 'Schylling', 'Anker'). Case-sensitive as passed to Amazon's refinement filter.
queryrequiredstringSearch keyword (e.g. 'usb cable', 'laptop').
categorystringAmazon department/category code passed as the 'i' parameter (e.g. 'electronics', 'books').
sold_by_amazonbooleanWhen true, filters results to only products sold by Amazon.com (excludes third-party marketplace sellers).
Response
{
  "type": "object",
  "fields": {
    "page": "string indicating the current page number",
    "products": "array of product objects with asin, title, price, rating, review_count, image, and total_sold"
  },
  "sample": {
    "data": {
      "page": "1",
      "products": [
        {
          "asin": "B07DD5YHMH",
          "image": "https://m.media-amazon.com/images/I/715afhb+qJL._AC_UY218_.jpg",
          "price": "$8.99",
          "title": "Anker Cable [2 Pack 3ft], USB A to USB C Cable",
          "rating": "4.7",
          "review_count": null
        }
      ]
    },
    "status": "success"
  }
}

About the Amazon API

Product Search and Detail

The search_products endpoint accepts a required query string and optional filters: category (Amazon department code), brand, sort order, and a sold_by_amazon boolean that restricts results to items fulfilled directly by Amazon. Results come back paginated — pass a page integer to navigate — with each product object carrying asin, title, price, rating, review_count, image, and total_sold (units bought in the past month when Amazon surfaces that figure).

The get_product_details endpoint takes a single asin and returns the full detail page: title, brand, price, description (array of bullet strings), specifications (key-value map of tech specs), images (array of high-resolution URLs), rating, review_count, and a rating_breakdown object with percentage shares for each star level (5_star through 1_star).

Reviews and Offers

get_product_reviews retrieves the customer review listing for an ASIN. Each entry in the reviews array includes author, rating, title, body, and date. A summary object at the top level repeats the overall star rating and total review count. get_product_offers returns all seller listings for an ASIN — useful for comparing third-party marketplace pricing against the main offer.

Best Sellers, Deals, and Cart

get_best_sellers accepts an optional category path segment (e.g. electronics, books) and defaults to the site-wide rankings when omitted. Each item in the response includes rank, asin, title, price, rating, review_count, image, and total_sold. get_deals requires no inputs and returns the current deals page as an array of objects with asin, title, price, and image. Two cart endpoints round out the API: add_to_cart (POST with asin and optional quantity) and get_cart (returns items array and subtotal string).

Reliability & maintenanceVerified

The Amazon API is a managed, monitored endpoint for amazon.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when amazon.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official amazon.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
1d ago
Latest check
7/7 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Track price changes for a watchlist of ASINs using get_product_details on a scheduled interval.
  • Build a comparison tool that pulls specifications and rating_breakdown for multiple ASINs side-by-side.
  • Aggregate best-seller rankings across categories via get_best_sellers to spot trending products.
  • Feed get_product_reviews results into a sentiment analysis pipeline for brand monitoring.
  • Surface live promotional pricing by polling get_deals and cross-referencing with normal prices.
  • Identify lowest-cost marketplace sellers for a product using get_product_offers.
  • Filter search_products by brand and sold_by_amazon to build a curated storefront for a specific manufacturer's first-party listings.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Amazon have an official developer API?+
Yes. Amazon offers the Product Advertising API 5.0 (PA-API), documented at https://webservices.amazon.com/paapi5/documentation/. It requires an Amazon Associates account and enforces strict usage terms tied to affiliate activity. The Parse API has no such affiliate requirement.
What does `rating_breakdown` contain, and when is it null?+
rating_breakdown is an object with keys 5_star, 4_star, 3_star, 2_star, and 1_star, each holding a percentage string (e.g. '72%'). Amazon only surfaces this breakdown on products with a sufficient number of reviews, so the field is returned as null for products where that breakdown is not present on the detail page.
Does the API expose seller profile details inside `get_product_offers`?+
The get_product_offers response currently returns an array of offer objects for an ASIN. Detailed seller profiles — seller ratings, fulfillment metrics, or storefront data — are not included. You can fork the API on Parse and revise it to add a dedicated seller-detail endpoint if that data is needed.
Does pagination work the same across all listing endpoints?+
search_products accepts a page integer parameter for paginating through results. get_best_sellers, get_deals, and get_product_reviews do not currently expose a pagination parameter — they return a single page of results. You can fork the API on Parse and revise those endpoints to add page controls.
Are product availability or inventory stock levels returned?+
Neither search_products nor get_product_details returns an explicit in-stock or inventory count field. Price and offer data from get_product_offers can serve as an indirect availability signal. You can fork the API on Parse and revise it to surface availability text if the product page exposes it.
Page content last updated . Spec covers 8 endpoints from amazon.com.
Related APIs in EcommerceSee all →