Amazon Product Search API

Amazon Product Search

Features

• Storefront-scoped queriesPair a non-empty product query with one supported Amazon domain so the requested storefront is explicit.
• Controlled result volumeSet an integer results_limit from 1 through 2,000; the collector stops at the requested cap or when no more source records are available.
• Normalized product identityReceive stable product fields for ID, type, source URL, title, description, publication time, and collection time.
• Commerce contextUse available seller, price, rating, review-count, sold-count, and media fields without parsing storefront-specific result shapes.

Parameters

How to Use

Choose the intended storefront and a concrete product phrase, then submit one asynchronous request.

1. Set a non-empty query, provide a supported Amazon domain URL, and choose results_limit from 1 through 2,000.
2. POST the request to /v1/amazon/product-search and save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task reaches succeeded or failed.
4. After success, read data.results.items and pass next_cursor while has_more is true.

curl -X POST "https://api.socq.ai/v1/amazon/product-search" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"wireless earbuds","domain":"https://www.amazon.com","results_limit":3}'

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

Best Use Cases

• Storefront product discovery: Find public products matching a category, feature, brand, or purchase-intent phrase in one supported Amazon storefront.
• Offer comparison: Compare available price amounts, currencies, formatted prices, and seller identity across returned products.
• Reputation screening: Review available ratings, review counts, and sold counts while preserving missing signals as unavailable.
• Catalog enrichment: Enrich product candidates with normalized titles, descriptions, source URLs, media, sellers, and collection timestamps.

Pro Tips

• Store the submitted query and domain with each task because the same phrase can produce different storefront results.
• Choose results_limit for the volume you need: it determines the reserved result estimate, while final billing settles against returned records.
• Follow next_cursor until has_more is false when a succeeded task contains more than one stored result page.
• Treat missing seller, price, rating, review-count, sold-count, or media values as unavailable rather than zero or an empty identity.

Related APIs