SUUMO Rental Scraper (Japan) avatar

SUUMO Rental Scraper (Japan)

Pricing

from $0.40 / 1,000 results

Go to Apify Store
SUUMO Rental Scraper (Japan)

SUUMO Rental Scraper (Japan)

Rental listings from SUUMO (suumo.jp), Japan's largest property portal. Search by prefecture (Tokyo, Chiba, Saitama, Kanagawa). One normalized record per room advert: rent in JPY, layout, area, nearest station + walk minutes, images, URL. Plain HTTP, no proxy or browser. Fresh data every run.

Pricing

from $0.40 / 1,000 results

Rating

0.0

(0)

Developer

Philip Kirkbride

Philip Kirkbride

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 hours ago

Last modified

Categories

Share

A plain-HTTP, no-proxy Apify Actor that extracts public rental listings from SUUMO (suumo.jp, Recruit) — Japan's largest property portal — into a single normalized record shape: rent in integer JPY, management fee, area, layout, nearest station and walking minutes, address, images and listing URL.

Access lane (verified live 2026-09-30, issue #213)

  • The chintai ichiran list page serves the full server-rendered result set over plain HTTP with a browser-grade User-Agent — no proxy, no browser, no challenge. Probe: ?ar=030&bs=040&ta=13&pc=50 → 200, 688 KB, ~3,906 cassette-item markers; &page=2 → 200, 554 KB, ~3,263 markers.
  • No captcha markers, no wall. The Store incumbents (fatihtahta/suumo-japan-scraper, sian.agency/suumo) scrape the same data through residential proxies — this lane gets it at $0 datacenter egress.
  • URL grammar (the incumbents' stable contract): /jj/chintai/ichiran/FR301FC001/?ar={area}&bs={business}&ta={todo}&pc={perPage}. bs=040 is the rental business code, pc=50 fixes 50 entries/page; page 1 is the bare URL and pages 2+ append &page=N.
  • The list page carries only BreadcrumbList JSON-LD, so the cassette HTML is the source of truth (no JSON-LD extraction needed).

Input

  • prefecture — 13 Tokyo (default), 12 Chiba, 11 Saitama, 14 Kanagawa. Each code pins the site's JIS prefecture code (ta) and its parent region (ar=030, Kanto) by construction.
  • maxPages — 1–5 list pages (50 entries per page, default 1)
  • maxResults — 1–200 room adverts (default 50)
  • requestDelaySecs — 0.5–10 s between page requests (default 1.0)

Output (dataset)

One record per room advert (a building with several rooms yields several rows):

fieldnotes
listing_keystable composite key suumo.jp:{prefecture}:{url}|{layout}|{area}|{rent} — dedupe on this
urlroom detail URL (falls back to the building page when a room row carries no own link)
building_name建物名 from the cassette cassetteitem_content-title text (never a 詳細を見る link label)
address所在地 from the cassette detail block
property_type賃貸マンション / 賃貸アパート / …
layout間取り (1LDK, 2DK, ワンルーム, …)
area_m2専有面積 in m²
rent_jpymonthly rent normalized from 万円 (8.3万円 → 83000)
management_fee_jpy管理費 in JPY when quoted
nearest_station / walk_minstation from 交通 (slash form JR中央線/八王子駅) and 歩N分 / 徒歩N分 on the nearest line (null on bus-only lines)
imagescassette image URLs (lazy-load placeholders excluded)
prefecture / prefecture_code / source / scraped_atrequest scope + provenance

Example input

{"prefecture": "13", "maxPages": 2, "maxResults": 100}
{"prefecture": "14", "maxResults": 50}

Notes

  • A persistent 403 raises BlockError immediately (there is no proxy lane to rotate onto): a wall on >50 % of requests is the issue's kill criterion — close the lane with evidence rather than silently retrying.
  • The four Kanto prefectures are the probe-verified minimum. Another region means probing and pinning its ar code first — never guessing it.
  • Not yet deployed (no Apify credentials in the build environment); push with apify push from this folder when deploying.

Cost

~0.6–0.7 MB HTML per page, no proxy: ≈ $0.0002–0.0004 per default (1-page) run, ≈ $0.001 at the 5-page cap. The incumbents' residential lanes are replaced by $0 datacenter egress.