Japan Real Estate Transaction Prices (Tokyo 23 Wards)

What does Japan Real Estate Transaction Prices do?

Purpose-built for Tokyo's 23 wards: this Actor turns raw government transaction records into district-level median/quartile price per m² that's ready to drop into a spreadsheet or dashboard — not 29 raw string columns you have to clean yourself. Data comes directly from Japan's official government source, the Real Estate Information Library (不動産情報ライブラリ), operated by the Ministry of Land, Infrastructure, Transport and Tourism (MLIT). You get every disclosed transaction (price, floor area, price per sqm, building year, structure, land use) for the wards, years and quarters you choose, either as individual records or pre-aggregated per-district statistics (median, 25th/75th percentile price per sqm, and a year-by-year trend).

The raw government API is free, but it's Japanese-only, undocumented in English, split into one call per municipality × year × quarter, and returns unlabeled string fields with no price-per-sqm or district-level statistics. This Actor removes that friction and adds the aggregation layer on top, running on Apify's infrastructure with scheduling, API access, and export built in.

Why use this Actor?

• Market research for foreign buyers and investors — Tokyo real estate (including the growing interest in akiya/vacant homes and central-ward condos) is a frequent target for international buyers who can't easily read Japanese government portals.
• PropTech and analytics products — drop clean, ward/district-level price statistics into your own app or dashboard without building a scraper or reverse-engineering the MLIT API.
• Due diligence — sanity-check a listing price against the actual disclosed transaction history for its district.

How to use Japan Real Estate Transaction Prices

1. Get a free API key from MLIT at reinfolib.mlit.go.jp. It's free, but goes through an application review — MLIT doesn't publish a guaranteed turnaround time, so apply before you need the data rather than expecting same-day access.
2. Paste the key into the MLIT reinfolib API key input field.
3. Pick one or more of Tokyo's 23 wards (by Japanese name, e.g. 渋谷区) and a year range.
4. Click Start and download the results as JSON, CSV, or Excel from the Dataset tab.

Input

Field	Type	Description
apiKey	string	Your free MLIT reinfolib API key (kept secret in the input form)
municipalities	array	Tokyo ward names (e.g. 渋谷区) or 5-digit MLIT municipality codes
yearFrom / yearTo	integer	Year range (data available from 2005)
quarters	array	Which quarters (1-4) to include; default all four
priceClassification	string	01 = transaction prices (default), 02 = agent-reported contracted prices
aggregate	boolean	true (default) = one row per district with median/quartile stats; false = every individual record
maxRequests	integer	Safety cap on API calls per run (default 200)

Example input:

{
  "apiKey": "your-mlit-reinfolib-api-key",
  "municipalities": ["千代田区", "港区", "渋谷区"],
  "yearFrom": 2022,
  "yearTo": 2025,
  "aggregate": true
}

Output

Aggregated mode (default) — one row per municipality + district:

{
  "municipalityCode": "13101",
  "municipality": "千代田区",
  "district": "一番町",
  "transactionCount": 6,
  "priceComputableCount": 6,
  "yearRange": [2022, 2025],
  "medianPricePerSqmJpy": 2986842,
  "p25PricePerSqmJpy": 2125000,
  "p75PricePerSqmJpy": 3939850,
  "yearlyBreakdown": [{ "year": 2024, "count": 6, "medianPricePerSqmJpy": 2986842 }],
  "source": "MLIT Real Estate Information Library (reinfolib.mlit.go.jp) XIT001",
  "credit": "このサービスは、国土交通省の不動産情報ライブラリのAPI機能を使用していますが…"
}

Raw mode (aggregate: false) — one row per disclosed transaction, with municipalityCode, district, period, type, tradePriceJpy, areaSqm, pricePerSqmJpy, buildingYear, structure, use, source, and credit fields.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Aggregated mode (default) — one row per municipality + district:

Field	Type	Description
municipalityCode	string	5-digit MLIT municipality code (e.g. 13101)
municipality / district	string	Ward and district name
transactionCount	number	Number of disclosed transactions in the requested period
priceComputableCount	number	Of those, how many had both a price and an area so a price-per-sqm could be computed (used for the stats below)
yearRange	array	[minYear, maxYear] covered by this district's transactions
medianPricePerSqmJpy / p25PricePerSqmJpy / p75PricePerSqmJpy	number	Median and quartile price per sqm (JPY)
yearlyBreakdown	array	Per-year count and median price per sqm
credit	string	Required MLIT attribution/disclaimer notice (see Legal section below)

Raw mode (aggregate: false) — one row per transaction:

Field	Type	Description
municipalityCode	string	5-digit MLIT municipality code
district	string	District name
period	string	Reporting period as given by MLIT (e.g. 2024年第4四半期)
type	string	Transaction type as reported by MLIT (e.g. land, land and building)
tradePriceJpy	number	Disclosed transaction price (JPY)
areaSqm	number	Floor/land area (sqm)
pricePerSqmJpy	number	Computed price per sqm
buildingYear / structure / use	string	Building attributes as reported by MLIT
source	string	Data source citation
credit	string	Required MLIT attribution/disclaimer notice (see Legal section below)

Pricing / cost estimation

This Actor uses Pay-Per-Event pricing: a small flat fee when a run starts, plus a per-result fee for each district-summary row or raw record returned. There is no charge for the underlying MLIT API itself — it's free — you're paying for the aggregation, cleaning, and Apify infrastructure (scheduling, storage, export).

Tips

• Start with a narrow year range and a couple of wards to check the shape of the data before running a large multi-year, all-23-ward pull.
• Use aggregate: true (default) for market research and dashboards — it's far cheaper and faster than pulling every raw record.
• maxRequests caps the number of (ward × year × quarter) API calls in a single run — raise it if you need multi-year, multi-ward coverage in one go.

FAQ, disclaimers and support

• All data originates from MLIT's official Real Estate Information Library under Japan's PDL 1.0 open data license — see the Legal section below for the full attribution requirements.
• Limitations: Currently supports Tokyo's 23 special wards only; other Japanese municipalities can be queried with a raw 5-digit MLIT municipality code but are not yet name-mapped. Nationwide coverage (name-mapping for all Japanese municipalities) is on the roadmap.
• Found an issue or need coverage for another prefecture? Use the Issues tab on this Actor's page.

Source, attribution and disclaimer

出典：国土交通省 不動産情報ライブラリ (Source: Real Estate Information Library, Ministry of Land, Infrastructure, Transport and Tourism of Japan). This Actor's output is created by the Actor author by editing and aggregating data from the Real Estate Information Library; it is not published or endorsed by MLIT. The data is provided under Japan's Public Data License v1.0 (PDL1.0), which permits commercial use with attribution.

As required by the Library's API terms, every result row carries this notice in its credit field: "This service uses the API function of the Real Estate Information Library of Japan's MLIT, but the latest information, accuracy, and completeness of the provided data are not guaranteed." If you display or redistribute the data, keep the attribution and this notice with it.

This data is for reference only and is not investment, legal, or tax advice. Verify against official records before any purchase, sale, or investment decision.

Your MLIT API key is entered as a secret input, is used only to call the Library API on your behalf during your own runs, and is never logged or stored by this Actor. Under the Library's terms you are responsible for keeping your key private.