Is this the same as general marketplace scraping?

No. Auction data carries an end timestamp and a realised price, which is what distinguishes a valuation signal from an asking price.

Can I filter by keyword or category?

Runs are driven by the search terms you supply, so you scope a run to the series, maker or category you care about.

What about sold lots?

Closed lots keep their end timestamp, so you can separate realised prices from still-live listings.

Japan Market Data › Mandarake Auction Data API

Mandarake Auction Data API

Mandarake is one of the reference price sources for second-hand Japanese collectibles. Its auction floor is where rare figures, vintage manga runs and unopened trading card boxes settle at their true market clearing price — not the optimistic number a seller types into a marketplace listing.

This scraper turns Mandarake auction pages into structured JSON. For anyone pricing a collection, sourcing stock, or building a valuation model, it replaces manual page-by-page checking with a dataset you can query.

Mandarake Auction Scraper → All Japanese market scrapers →

What you get

`item_name`	Auction lot title, including series and edition markers.
`current_price_jpy`	Current bid or hammer price in yen.
`condition`	Grade where the lot publishes one.
`item_url`	Direct lot URL.
`image_url`	Lot photograph.
`sold_at`	Auction end timestamp for closed lots.

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

Valuation: compare a graded figure's asking price against what auction lots actually cleared at.
Sourcing: find categories where the auction clearing price sits below overseas retail.
Catalogue building: pull images and titles for a storefront or database.

How a run works

Starting a run: call the Apify API with the actor id fruitful_quintessence~mandarake-auction-scraper, or press Start on the actor page and download the dataset. Check the actor page for its exact input schema — a run is scoped by the search terms you supply, and billing is per result returned (roughly $0.002 per item).

curl -X POST "https://api.apify.com/v2/acts/fruitful_quintessence~mandarake-auction-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["your", "search", "terms"]}'

FAQ

Is this the same as general marketplace scraping?: No. Auction data carries an end timestamp and a realised price, which is what distinguishes a valuation signal from an asking price.
Can I filter by keyword or category?: Runs are driven by the search terms you supply, so you scope a run to the series, maker or category you care about.
What about sold lots?: Closed lots keep their end timestamp, so you can separate realised prices from still-live listings.

What you get

Use cases

How a run works

FAQ

Related