Japan Market Data › Japan Price Monitoring API
Price monitoring is a diff problem. You need the same field, measured repeatedly, keyed on something stable. Japanese marketplace listings are well suited to this because the listing URL persists while the price changes.
Running the scrapers on a schedule and matching records on item_url produces a time series per item with very little engineering. From there, alerting is a comparison, and reporting is a chart.
item_url | Stable key for matching records across runs. |
|---|---|
current_price_jpy | The field you diff. |
condition | Guards against false positives when condition differs. |
sold_at | Marks a listing as ended so it can be retired from the watchlist. |
Field names follow the actor's dataset schema and can differ slightly between actors — check the actor page for the exact input and output schema before wiring it into a pipeline.
Starting a run: pick the actor for your marketplace from the publisher page, then start it from the Apify console or the API. Billing is per result returned (roughly $0.002 per item), so a scoped search stays cheap.
curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?token=$APIFY_TOKEN&format=json"