Where does the data come from?

The national MLIT Reinfolib transaction price dataset, queried through the actor. It is official government-published transaction data rather than portal listings.

How current are the records?

The underlying dataset is updated periodically by the ministry, so treat the returned set as the latest published batch rather than real-time sale prices.

Can I filter by prefecture or period?

Yes — the run is scoped by the query parameters you supply, which is what makes prefecture-level and period-level analysis practical.

Japan Market Data › Japan Real Estate Price Data

Japan Real Estate Price Data

Japanese property listing portals show asking prices, which is a different number from what transactions actually cleared at. For any serious valuation work the useful figure is the recorded transaction price, and in Japan that data is published by the government through the MLIT Reinfolib dataset.

This actor queries that dataset and returns structured JSON: transaction price, floor area, location, building information and zoning, covering all 47 prefectures. Because the underlying source is the official land and property transaction record rather than a broker's listing, it stands up as evidence in an appraisal or investment memo.

Japan Real Estate Transaction Prices API → All Japanese market scrapers →

What you get

`transaction price`	Recorded price for a completed transaction, in yen.
`area`	Land or floor area for the transaction, as recorded.
`location`	Prefecture, municipality and district metadata.
`building info`	Structure, use and construction details where recorded.
`zoning`	District and zoning classification tied to the parcel.

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

Build a comparable-sales set for an appraisal instead of relying on asking prices.
Screen which municipalities transact at the strongest price per square metre.
Feed a property dashboard with official figures that a client can verify at source.

How a run works

Starting a run: call the Apify API with the actor id fruitful_quintessence~mlit-japan-property-prices, 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~mlit-japan-property-prices/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["your", "search", "terms"]}'

FAQ

Where does the data come from?: The national MLIT Reinfolib transaction price dataset, queried through the actor. It is official government-published transaction data rather than portal listings.
How current are the records?: The underlying dataset is updated periodically by the ministry, so treat the returned set as the latest published batch rather than real-time sale prices.
Can I filter by prefecture or period?: Yes — the run is scoped by the query parameters you supply, which is what makes prefecture-level and period-level analysis practical.

What you get

Use cases

How a run works

FAQ

Related