Japan Market Data › Japan Resale Market Data

Japan Resale Market Data

Single-source price data is easy to collect and easy to misread. A figure that looks expensive on one marketplace may be the cheapest copy on another, and a category that seems to be rising may simply have shifted from auction listings to fixed-price ones.

Pulling from several Japanese sources and keeping the records separate lets you see the spread instead of a single number: auctions for realised prices, C2C marketplaces for consumer asks, dedicated collectible floors for specialist grades.

Browse all Japanese market scrapers → All Japanese market scrapers →

What you get

item_nameProduct title as published by the source.
current_price_jpyPrice in yen, consistent across sources.
conditionSource-published grade.
item_urlSource listing URL — also identifies which marketplace a record came from.
sold_atPresent for auction sources; absent for live fixed-price listings.

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.

Use cases

How a run works

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"

FAQ

How do I combine sources without double counting?
Keep the source URL with each record; identical items rarely share a URL, and deduplication by title plus price band handles the rest.
Should I trust asking prices?
Use them to see supply and competition. Use auction end prices when you need a defensible value.
Does one run cover all marketplaces?
They are separate actors, so you decide which sources to run and at what frequency.

Related