Guide | first launch wedge

Use Products watch routes

Search products, inspect offers and price history, then register a source-bounded watch with a stable SmartAPIs.net request contract. This is the first focused revenue path; product data remains snapshot-backed and should not be treated as merchant-official checkout truth.

1. Search reviewed products

curl

curl \
  -H "X-API-Key: $SMARTAPIS_API_KEY" \
  "https://smartapis.net/v1/products/search?region_id=new-york-city&q=charger&brand=Northlight&limit=5"

2. Inspect offers and price history

curl

curl \
  -H "X-API-Key: $SMARTAPIS_API_KEY" \
  https://smartapis.net/v1/products/product_nyc_001/offers

curl \
  -H "X-API-Key: $SMARTAPIS_API_KEY" \
  https://smartapis.net/v1/products/product_nyc_001/price-history

Product identity fields are source-grounded. Offer and price-history results are SmartAPIs snapshot outputs built from reviewed source feeds.

3. Register a product watch intake

curl

curl -X POST \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $SMARTAPIS_API_KEY" \
  -d '{
    "region_id": "new-york-city",
    "query": "charger",
    "brand": "Northlight",
    "trigger": "daily_price_snapshot_change",
    "delivery_channel": "email_confirmation_only",
    "cadence_hours": 24
  }' \
  https://smartapis.net/v1/products/watch

The watch route is an honest intake surface for product-monitoring workflows. It is suitable for stable app and agent integration when paired with freshness, provenance, and price-change caveats in your UI.

4. Preserve trust boundaries

  • Show product and offer data as snapshots, not guaranteed live checkout facts.
  • Keep source and freshness metadata attached where your app exposes results.
  • Route uncertain price or availability changes to human review when money moves.