Japan Residential Rental Listings Bulk — SUUMO & Yahoo
Pricing
$1.00 / 1,000 residential rental listing exporteds
Japan Residential Rental Listings Bulk — SUUMO & Yahoo
Export paginated Japan residential rental rooms by city from SUUMO and Yahoo! Real Estate with normalized yen rent, fees, area, floor plan, use-case tags, per-source status and resume cursors. Bounded partial coverage.
Pricing
$1.00 / 1,000 residential rental listing exporteds
Rating
0.0
(0)
Developer
h ichi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Japan Residential Rental Listings Bulk
Export public residential rental rooms from SUUMO and Yahoo! Real Estate in bounded city batches. Sources are independently selectable and have separate parsers, IDs, status, and resume cursors. Two portals are not an all-site or complete nationwide snapshot.
Input
Provide one five-digit JIS municipality cityCode (for example 13113 for Shibuya-ku) and sources (suumo, yahoo-realestate, or both). Each source has its own StartPage and StartRoomOffset fields for resumption. maxPagesPerSource is 1-25 (default 5), maxItems is 1-4000 (default 500) across selected sources, and useCase is all, solo, couple, or family. Solo means a 1R/1K/1DK plan, couple means a 1LDK/2K/2DK plan with at least 30 m2, and family means 2LDK or 3K+ with at least 45 m2; these are sorting heuristics. Optional maxMonthlyJpy filters known rent plus management fee. maxDetailPagesPerSource (0-15, default 0) limits extra public detail checks on each selected source.
Output
A listing row contains one unique source-prefixed rental-room ID, normalized yen rent and known fees, plan, square meters, area, source URL, heuristic use-case tags, page position and fetched-at time. Each selected source gets an uncharged source_status checkpoint before listing export (statusPhase=checkpoint), then a final status after its listing batches succeed (statusPhase=final). The checkpoint has itemsEmitted=0 and the requested start page/room offset as its conservative resume cursor. If export stops before the final status, resume from that checkpoint and deduplicate any replayed rows by sourceListingId. Final status records ok, partial, or failed, actual exported count, the collection-end cursor, fetched page count, source hit count, truncation reason, and a controlled error code/message if needed. sourceTotalFound is each site's claim, never the number exported; it is omitted if the source count was not observed. Final truncatedBy is item-limit, page-limit, time-limit, source-end, or source-error; checkpoints use publish-in-progress. nextPage=0 means the source has no proven next page. Results can shift between runs; deduplicate by the full source-prefixed sourceListingId. Do not merge a possible cross-portal duplicate by address or price. Missing fees or deposits remain absent, not zero. Foreign-national consultation wording is only evidence that inquiry may be possible: foreignerAcceptanceStatus is always unverified, including where the source says 外国人相談可.
Optional detail checks require the requested room’s canonical URL and source-specific detail markup. A blocked, stale, wrong-room, or incomplete detail remains not-checked with no evidence code and a partial source status carrying the error. Validated list rows remain exportable; detail checks never incur a separate charge. HTTP 200 block/verification pages are reported as auth-block, while missing room identity or markup is structure-change.
Pricing
Provisional PPE hypothesis, requiring owner confirmation before publication: $0.001 per unique, validated listing row successfully exported as rental-listing-scraped; source-status rows, page requests and optional detail checks have no event. A partial run charges only emitted listing rows. Empty runs fail without a listing charge; a source failure is explicit even when another source returns usable rows.
Limits
At most 25 sequential list pages and 15 optional room details per selected source plus one cached robots.txt request per selected host (82 requests total), 4,000 unique rows, 5 MiB per response, 30 seconds per request and 300 seconds per run. Collection stops starting requests after about 120 seconds; one final request may use another 30 seconds, reserving about 150 seconds for batched dataset export and final statuses. Requests to the same host are spaced at least 1.5 seconds apart. SUUMO newest-first and Yahoo site-default ordering can shift or favor some listings; partial extraction is labelled and is not a representative city-wide sample. Current robots rules are retrieved once per selected host and checked before each list/detail request, including wildcard and end-anchored restrictions; unverified rules fail closed. Redirects are rejected. No login, proxy, browser or paid external API is used.
Privacy
Only public property facts and controlled consultation-evidence codes are output. Broker or tenant names, phone numbers, email addresses, reviews, inquiry content, descriptive prose, photos and precise coordinates are excluded. Details are never interpreted as a binding acceptance decision. SUUMO, Recruit, Yahoo and LY Corporation do not endorse this product.