amazon/
best-sellers

The Amazon Best Sellers API collects products from public Amazon Best Sellers URLs, returning titles, seller context, prices, visible reputation signals, and media as normalized records.

Amazon Best Sellers API

Category URL input
Product records
0.15 credits per result
0.15 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Amazon Best Sellers

Amazon Best Sellers pages organize publicly visible products within category lists, with product titles, seller context, prices, ratings, review counts, sold counts, media, source links, and observation times available when exposed. SocQ turns selected list URLs into normalized product records for category research, assortment comparison, and repeatable commerce-data workflows.

Amazon Best Sellers API Features

  • Regional category URL collectionSubmit one or more public Best Sellers or category-list URLs across the supported Amazon marketplaces in a single asynchronous task.
  • Normalized product identityReceive stable product records with available IDs, titles, descriptions, source URLs, platform and resource labels, and collection timestamps.
  • Commerce and reputation contextKeep available seller details, price values, ratings, review counts, and sold counts in explicit fields rather than parsing page markup.
  • Media-ready product recordsUse normalized media objects with each product for catalogs, review queues, enrichment pipelines, and downstream visual analysis.

Amazon Best Sellers API Parameters

ParametersRequiredDescription
urlsRequiredRequired list of Amazon references on supported marketplace hosts or subdomains. Each path must contain /zgbs/ or /gp/bestsellers/. Any scheme with a parsed hostname and protocol-relative references are accepted.
results_limitOptionalOptional integer from 1 through 2,000. It defaults to 100 and caps the total unique product records saved across all submitted URLs.

How to Use the Amazon Best Sellers API

Submit known public Best Sellers URLs to the Amazon Best Sellers API, monitor the asynchronous task, and page through the normalized product records.

  1. Prepare one or more public Amazon Best Sellers or category-list URLs on a supported marketplace host.
  2. Send urls and an optional results_limit from 1 through 2,000 to /v1/amazon/best-sellers, then save the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
  4. Read data.results.items and request next_cursor while has_more remains true.
curl -X POST "https://api.socq.ai/v1/amazon/best-sellers" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.amazon.com/Best-Sellers-Books/zgbs/books"],"results_limit":3}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Amazon Best Sellers API Use Cases

  • Category assortment snapshots: Point the Amazon Best Sellers API at selected Best Sellers pages to build a bounded product inventory with source links and collection times for a defined research dataset.
  • Price and reputation comparison: Compare available prices, ratings, review counts, and sold counts across returned products without scraping inconsistent page markup downstream.
  • Product discovery enrichment: Add titles, seller context, descriptions, media, and public product URLs to shortlists discovered from category pages.

Amazon Best Sellers API Pro Tips

  • Use references on supported regional Amazon hosts whose paths contain /zgbs/ or /gp/bestsellers/. Unrelated Amazon paths are rejected before task creation.
  • Set results_limit for the entire Amazon Best Sellers API task, not for each submitted URL, and size it for the combined batch you need.
  • Follow next_cursor until has_more is false because task results are returned through a separate cursor-paginated results view.
  • Treat IDs, descriptions, seller data, prices, ratings, counts, media, URLs, and publication times as nullable rather than replacing missing values with zero or an empty object.
  • Store collected_at with each record and schedule separate runs when you need point-in-time comparisons; the endpoint does not create a continuous feed.

Beyond the Amazon Best Sellers API, use these APIs when you need a different type of public Amazon data.

  • Amazon Product Details API — Collect product details from known Amazon URLs with title, description, seller, price, rating, review-count, sold-count, and media fields.
  • Amazon Product Search API — Search a supported Amazon storefront by product phrase and return normalized product, seller, price, rating, review, sold-count, media, and source fields when available.
  • Amazon Reviews API — Collect public product reviews from supported Amazon URLs with text, ratings, author details, product references, timestamps, and media.
  • Amazon Seller Info API — Collect public Amazon seller-profile identity, description, website, rating, feedback, location, source, and collection-time fields from known seller URLs.
  • Amazon Storefront API — Read an Amazon creator storefront from its shop URL with profile, linked social accounts, idea lists with item counts, curated posts, and trending picks with prices.

Explore other platforms

Combine Amazon data with public data from other supported social platforms.

Amazon Best Sellers API — FAQ

Amazon Best Sellers API is a programmatic interface for collecting products from public Amazon Best Sellers or category-list URLs as normalized SocQ product records.

The urls array accepts references whose parsed hostname is a supported Amazon marketplace or subdomain and whose path contains /zgbs/ or /gp/bestsellers/. Any scheme with a hostname and protocol-relative references are accepted.

No rank field is part of the stable product response. The normalized record focuses on product identity, content, seller, price, rating, review and sold counts, media, URLs, and timestamps when available.

results_limit defaults to 100, accepts integers from 1 through 2,000, and caps the total unique records saved for the task across all input URLs. It is not a separate allowance for every URL.

Poll /v1/tasks/{task_id}, read data.results.items after success, and keep requesting the returned next_cursor while has_more is true. The result-page limit controls retrieval pagination, not collection volume.

Public availability, page contents, provider output, normalization, deduplication, and the task-wide results_limit can all reduce the final result count. A successful task can also contain no product records.

The Amazon Best Sellers API charges 0.15 SocQ credits for each successfully returned standard product record. The task reserves credits using results_limit, or 100 when it is omitted, then settles against the actual returned count and refunds unused reserved credits; an empty result has no result charge.