Amazon Product Details API

Amazon Product Details

Features

• Batch lookup from known product URLsSubmit one or more Amazon URLs in a single task and receive no more normalized product records than the number of valid URLs supplied.
• Product identity, copy, and mediaEach record can include the product identifier and URL, title, description, collection timestamp, and available image or video references.
• Seller, price, and visible product signalsNested seller and price objects sit alongside rating, review-count, and reported sold-count fields for consistent field-level processing.
• Supported Amazon marketplace hostsThe URL validator accepts Amazon hosts for the United States, United Kingdom, Germany, France, Spain, Italy, Canada, Australia, India, and Japan, including their subdomains.

Parameters

How to Use

Submit known product URLs, save the asynchronous task ID, and read normalized product records after the task succeeds.

1. POST a urls array to /v1/amazon/product-detail using a Bearer token or API key.
2. Save the returned task_id and poll GET /v1/tasks/{task_id} until status becomes succeeded or failed.
3. Read data.results.items after success; when has_more is true, request the next result page with next_cursor without submitting another product task.

curl -X POST "https://api.socq.ai/v1/amazon/product-detail" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.amazon.com/dp/B0CHHSFMRL"]}'

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

Best Use Cases

• Known-item catalog enrichment: Attach product titles, descriptions, seller context, prices, media, ratings, and counts to an existing set of Amazon URLs.
• Point-in-time product comparison: Compare normalized price, currency, rating, review count, sold count, and seller fields across selected product records collected at the same time.
• Product source verification: Use identifiers, canonical URLs, titles, descriptions, media references, and collection timestamps to review stored catalog references against public product pages.

Pro Tips

• Use product references whose parsed hostname belongs to a supported Amazon marketplace; a valid host alone does not guarantee that the target resolves to a public product record.
• Do not send results_limit because this endpoint fixes its provider result cap to the number of submitted URLs.
• Treat seller, price, rating, review-count, sold-count, media, URL, and publication-time fields as nullable, and preserve a succeeded task with zero items instead of creating placeholder data.
• Use next_cursor only when paging through stored task results; continue GET requests for the same task rather than repeating the paid POST.

Related APIs