SUUMO Property Scraper for the Japanese Market
SUUMO is a major Japanese property portal, and its listing pages mix sale prices, rental rates, floor plans, agent contacts and neighborhood context.
This page explains how to send a SUUMO URL through a single HTTP request and receive either rendered HTML or parsed JSON, with optional controls for JavaScript, geotargeting, proxy type and AI-driven extraction. It is written for developers and data teams building Japanese property-market analysis, rental-yield models or relocation pricing tools.
What a SUUMO request can return
A single SUUMO listing page can yield asking price or rent, number of bedrooms, floor area in square meters, neighborhood and city, agent name, days on market and the listing's image gallery. The same request can return the fully rendered HTML if you prefer to parse it yourself, or structured JSON if you supply extraction rules. Three common workflows are property listing collection, rental-rate tracking by neighborhood over time, and amenity lookup around an address for location-based analysis.
How a request flows
You create an account, receive an API key and a starting credit balance, then send a request containing your key and a SUUMO URL. The service rotates proxies, spoofs browser fingerprints and renders JavaScript behind the scenes, so the response arrives ready to parse. You can start in the dashboard request builder, paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL before moving it into your codebase.
Control map: which parameter to reach for
Use this map to pick the right control for the problem in front of you.
- Page content is missing because it is built by JavaScript: set render_js=true. The page runs in a real headless browser and you receive the post-render HTML.
- The target shows a CAPTCHA or blocks your IP: enable stealth_proxy. Premium proxies cost more credits per successful request than classic proxies.
- Content differs by country: pass country_code to route through a residential IP in that country.
- You want parsed fields rather than HTML: pass extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language description of the fields you want.
- You need a visual record: request a full-page screenshot.
- You need to click, scroll or type before capture: use a JavaScript scenario.
- You want LLM-ready text: request the page as Markdown.
- You want no scraper code at all: build the workflow in n8n and call the API from there.
Worked example: one SUUMO URL to a listing record
Suppose you want a record for a single SUUMO sale listing with price, bedrooms, floor area, neighborhood and agent name. Send the listing URL with render_js=true so the page is fully built, then attach extract_rules that map CSS selectors to those five field names. The response is parsed JSON you can write straight into a table. If the page structure is unfamiliar or changes often, replace the selector map with ai_extract_rules and describe the fields in plain language instead. The same pattern works for rental listings: swap the price selector for the monthly rent field and keep the neighborhood and agent fields unchanged.
Telling failures apart
Not every empty or partial response means the same thing, and the fix differs.
- Empty shell with no listing content: JavaScript has not run. Add render_js=true.
- CAPTCHA page or access-denied page: the request was fingerprinted or IP-blocked. Enable stealth_proxy and, if the content is region-specific, set country_code.
- Correct page but missing fields: your selectors no longer match the page. Inspect the rendered HTML, update extract_rules, or switch to ai_extract_rules.
- Repeated throttling from the target: the API applies concurrency limits per plan rather than per-target rate limits, so space requests out or use multiple sessions if the target reacts badly to bursts.
Credits, concurrency and plan shape
API credits are valid for one month and do not roll over. A basic request starts at one credit. Enabling JavaScript rendering costs five credits per successful request. Enabling premium proxies costs ten credits per successful request without JS rendering, or twenty-five with it. Concurrency is the number of requests that can be in flight at the same time, and it is set per plan. The full plan table below preserves every original row, price and feature line exactly as captured; treat those figures as a dated reference and confirm current pricing before you commit.
Languages and integrations
SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for any stack. The dashboard request builder generates a snippet in Python, Node, Go, PHP, Ruby or cURL from the parameters you set. For no-code workflows, n8n can call the API to monitor listings without writing scraper code. Markdown output is available when the next step is an LLM rather than a database.
| Plan | Monthly price | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
All prices are exclusive of VAT. Figures reflect the captured reference and should be confirmed against current pricing before purchase.
Frequently asked questions
Can I scrape SUUMO without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. For fully no-code workflows, n8n can call the API to monitor listings.
How do I handle JavaScript when scraping SUUMO?
Pass render_js=true on the request. The page runs in a real headless browser, JavaScript executes server-side, and you receive the post-render HTML.
Can I scrape SUUMO from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This matters when SUUMO content or availability varies by geography.
What's the rate limit for scraping SUUMO?
The API applies concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space requests out or use multiple sessions.
How do I get structured JSON from SUUMO?
Two routes produce parsed JSON. With extract_rules you supply a map of CSS selectors to your chosen field names, so each selector's matched content lands under that key. With ai_extract_rules you describe the fields you want in ordinary language and skip selector authoring entirely. Either way, the parsed JSON comes back in the response body.
Which programming languages can I use to scrape SUUMO?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.