Suumo Rental Listings Scraper — Japan Real Estate Data in English

Scrape rental listings (賃貸 / chintai) from Suumo (suumo.jp) — Japan's largest property portal — and get clean, English-normalized JSON: rent as a number in JPY, deposit and key money converted to months, building age in years, stations with walking minutes. No Japanese parsing needed on your side.

What it does

• Crawls Suumo rental search-result pages (~30 listings per page request — fast and cheap; no detail-page fetches in v1).
• Normalizes every Japanese value format for you: 12.5万円 → 125000, 新築 → age 0, 敷金 25万円 → deposit_months: 2, ワンルーム → 1R, "-" → null.
• Builds search URLs from prefecture/ward codes and rent bounds, or accepts any Suumo search URL you paste in.
• Typical uses: relocation research, Tokyo rent analytics, market dashboards, ML datasets, alerting on new listings in a ward.

Input

Field	Type	Default	Description
searchUrls	array of strings	—	Full suumo.jp rental search-result URLs (/jj/chintai/ichiran/FR301FC001/…). When set, the fields below are ignored.
prefectureCode	string	"13"	Two-digit JIS prefecture code (13 = Tokyo). v1 URL builder covers Kanto (08–14); elsewhere use searchUrls.
wardCodes	array of strings	["13101"]	Five-digit JIS municipality codes (13101 Chiyoda, 13104 Shinjuku, 13113 Shibuya, …).
minRentJpy / maxRentJpy	integer	—	Optional monthly rent bounds in JPY.
maxResults	integer	100	Hard cap per run (max 10,000). Free-plan users are capped at 50.
language	string	"en"	Output normalization language — v1 is English only.

Example input:

{
    "searchUrls": ["https://suumo.jp/jj/chintai/ichiran/FR301FC001/?ar=030&bs=040&ta=13&sc=13101"],
    "maxResults": 100
}

Output sample

One dataset item per advertised unit (a building can yield several):

{
    "title": "Ａｎｖｉｌｌｅ神田司町",
    "rent_jpy": 125000,
    "admin_fee_jpy": 10000,
    "deposit_months": 1,
    "key_money_months": 1,
    "layout": "1K",
    "size_m2": 25.2,
    "floor": "9F",
    "building_age_years": 10,
    "building_type": "condo",
    "address_ja": "東京都千代田区神田司町２",
    "stations": [
        { "line": "東京メトロ丸ノ内線", "station": "淡路町駅", "walk_min": 4 },
        { "line": "JR山手線", "station": "神田駅", "walk_min": 7 }
    ],
    "detail_url": "https://suumo.jp/chintai/jnc_000091230001/?bc=100510000001",
    "scraped_at": "2026-06-10T12:00:00.000Z"
}

Field notes: admin_fee_jpy, deposit_months, key_money_months, size_m2, floor, building_age_years are null when Suumo lists them as - (none / not provided). building_type is "condo" (マンション), "apartment" (アパート) or "house" (一戸建て). walk_min is null for bus/car access. Building names and addresses are kept in the original Japanese — they are proper nouns you'll need for maps and detail pages.

Pricing & free-tier policy

This Actor uses pay-per-event pricing:

Event	Price	When charged
Actor start (apify-actor-start)	$0.005	Automatically by Apify, once per run (per GB of memory)
Rental listing (apify-default-dataset-item)	$1.00 / 1,000 items	Automatically by Apify, per default-dataset item

You only pay for listings that pass output-schema validation — malformed rows are never charged. Set Maximum cost per run in Apify Console to cap spend; the Actor stops gracefully at the limit and keeps everything scraped so far.

Free tier — stated plainly: users on the Apify free plan get up to 50 listings per run. The run still finishes successfully with a clear status message when the cap is reached. Any paid Apify plan unlocks the full 10,000-listings-per-run limit.

Limitations

• Search-result pages only (v1). Fields shown only on detail pages (exact floor plans, photos, fees breakdown, agency info) are not included yet.
• Rental (chintai) only. Sales listings (新築/中古マンション etc.) are out of scope.
• Politeness by design: pages are fetched sequentially with a randomized 2–5 s delay, so very large runs take a while (~30 listings per fetch).
• The prefecture/ward URL builder covers the Kanto area block in v1; for other regions, paste full Suumo search URLs into searchUrls.
• Data is scraped from public Suumo pages; listings change constantly, so treat results as a snapshot (scraped_at is included on every row).

Support

Found an issue or need a field added? Open an issue on the Actor page and it will usually be handled within a few days.