Docs menu

Crawlora Docs

Build an Amazon Product Monitoring Workflow

Track product search and product-page signals such as price, availability, rating, and review count.

Overview

Track product search and product-page signals such as price, availability, rating, and review count.

What you will build

  • Define ASINs or keywords
  • Fetch product or search data
  • Store price, availability, rating, and review count
  • Compare snapshots
  • Alert on changes

APIs used

Only endpoints that exist in the generated endpoint metadata are linked here. Missing optional endpoints are intentionally omitted.

GETAmazonapiKey2 credits/request

Retrieve Amazon product details

/amazon/product/{asin}

Returns normalized product details for an Amazon ASIN on `amazon.com`, including pricing, availability, overview data, inline review samples, and descriptive content.

GETAmazonapiKey3 credits/request

Search Amazon products

/amazon/search

Returns normalized Amazon search result cards for `amazon.com`.

Data model

FieldNotes
asinWorkflow field; map to exact endpoint response fields from endpoint docs.
keywordWorkflow field; map to exact endpoint response fields from endpoint docs.
titleWorkflow field; map to exact endpoint response fields from endpoint docs.
priceWorkflow field; map to exact endpoint response fields from endpoint docs.
availabilityWorkflow field; map to exact endpoint response fields from endpoint docs.
ratingWorkflow field; map to exact endpoint response fields from endpoint docs.
review_countWorkflow field; map to exact endpoint response fields from endpoint docs.
sellerWorkflow field; map to exact endpoint response fields from endpoint docs.
checked_atWorkflow field; map to exact endpoint response fields from endpoint docs.

Step-by-step workflow

  1. 1.Define ASINs or keywords
  2. 2.Fetch product or search data
  3. 3.Store price, availability, rating, and review count
  4. 4.Compare snapshots
  5. 5.Alert on changes

Example request

This example uses the real Retrieve Amazon product details endpoint. Exact request fields come from the endpoint metadata.

Recipe request

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/amazon/product/B0DGJ736JM?language=en&currency=USD" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example response

Use endpoint detail pages for exact response schemas. This recipe does not invent response fields.

Generated example response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "asin": "B0DGJ736JM",
    "title": "Apple Watch SE (2nd Gen) [GPS 40mm]",
    "link": "https://www.amazon.com/dp/B0DGJ736JM/",
    "rating": 4.4,
    "review_count": 1055,
    "price": 189
  }
}

Storage/output suggestion

Store a current product table plus immutable snapshot rows for price and availability history.

Error handling

  • Validate required inputs before calling Crawlora
  • Retry 429 and temporary 5xx responses with capped backoff
  • Log endpoint, input, timestamp, and request ID when present
  • Treat empty results as a state your application can handle
  • Open /docs/errors for production retry guidance

Rate-limit and credit planning

Estimate usage by multiplying requests by endpoint credit cost. The table below only shows real credit costs available from the billing constants.

EndpointCredit costDocs
Retrieve Amazon product details2 credits/request/docs/Amazon/amazon-product
Search Amazon products3 credits/request/docs/Amazon/amazon-search

Production checklist

  • Keep API keys server-side
  • Use request timeouts
  • Back off on rate limits
  • Store raw responses or source IDs for auditability
  • Monitor credits and failures
  • Avoid unnecessary refreshes
  • Review responsible-use requirements

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

Related APIs and pages

Build this workflow with real endpoint docs

Use this recipe for workflow shape, then rely on endpoint reference pages for exact paths, request schemas, response schemas, and credit costs.