REAL ESTATE · JAPAN
SUUMO Rental (Japan)
Rental listings from SUUMO (suumo.jp), Japan's largest property portal.
About this data
Rental listings from SUUMO (suumo.jp), Japan's largest property portal. Search by prefecture including Tokyo, Chiba, Saitama and Kanagawa; one record per room advert: rent JPY, management fee, layout, area, station, walk time, address, images. On-demand — fresh every run.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/jp/suumo/rentals
Fetch one results page with up to 20 SUUMO rentals in Tokyo, Chiba, Saitama or Kanagawa.
Records include listing URLs, building names, addresses, floor plans, areas, monthly JPY rents and nearest-station walking times; management fees appear when published.
No detail pages are fetched.
Input
Send a JSON body to POST https://api.ssh.autos/v1/jp/suumo/rentals.
| Field | Type | Required | Notes |
|---|---|---|---|
prefecture | string | optional | one of 13, 12, 11, 14; default "13" |
maxResults | integer | optional | 1–20; default 10 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 16 fields; a field the source does not publish comes back null.
16 fields per record
| Field | Type | Notes |
|---|---|---|
listing_key | string | Stable composite key (source:prefecture:url|layout|area|rent); dedupe on this across runs. |
url | string | Canonical room detail URL on suumo.jp (falls back to the building page when a room row carries no own link). |
building_name | string | Building name (建物名) as shown on the cassette title. |
address | string | Address (所在地) from the cassette detail block. |
property_type | string | Property type label (賃貸マンション, 賃貸アパート, ...). |
layout | string | Layout / 間取り (1LDK, 2DK, ワンルーム, ...). |
area_m2 | number | Exclusive floor area (専有面積) in m². |
rent_jpy | integer | Monthly rent normalized to integer JPY (万円 x 10000). |
management_fee_jpy | integer | Monthly management fee (管理費) in integer JPY when quoted. |
nearest_station | string | Nearest station from the 交通 transit line (slash form 線/駅), e.g. 八王子駅. |
walk_min | integer | Walking minutes to the nearest station (徒歩N分 or the bare 歩N分); null when no walk leg is quoted (e.g. bus-only). |
images | array of strings | Image URLs from the cassette (placeholder/lazy-load stubs excluded). |
prefecture | string | Prefecture English name (Tokyo, Chiba, Saitama, Kanagawa). |
prefecture_code | string | JIS prefecture code used in the request (ta), e.g. 13. |
source | string | Source website hostname (suumo.jp). |
scraped_at | string | UTC ISO-8601 scrape timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/jp/suumo/rentals -m POST -b '{"prefecture": "13", "maxResults": 5}'
The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: SUUMO Rental Scraper (Japan). Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt