Guide

Use Places V2 routes

Move from the legacy list route to explicit search, nearby ranking, agent context, and bootstrap watch intake.

1. Search explicitly

curl

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

2. Rank nearby options

curl

curl \
  -H "X-API-Key: $SMARTAPIS_API_KEY" \
  "https://smartapis.net/v1/places/nearby?latitude=40.7580&longitude=-73.9855&radius_km=3&q=pizza&limit=5"

3. Fetch place-level context

curl

curl -H "X-API-Key: $SMARTAPIS_API_KEY" \
  https://smartapis.net/v1/places/place_nyc_001/hours

curl -H "X-API-Key: $SMARTAPIS_API_KEY" \
  https://smartapis.net/v1/places/place_nyc_001/status

curl -H "X-API-Key: $SMARTAPIS_API_KEY" \
  https://smartapis.net/v1/places/place_nyc_001/agent-context

Hours, status, and agent-context should be treated as SmartAPIs reference summaries unless the payload explicitly marks a field as source-grounded.

4. Register a bootstrap watch

curl

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

The current watch route is an honest bootstrap intake surface, not yet a full durable notification product.