# SUUMO Japan Property Scraper (Rentals & Sales) (`stone_jadex/suumo-japan-property-scraper`) Actor

Public SUUMO (suumo.jp) rental and sale listings: propertyId, rent/price in yen, layout, area, station walk, address, fees, photos. Optional detail page. No start fee. Draft PPE only.

- **URL**: https://apify.com/stone_jadex/suumo-japan-property-scraper.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Categories:** Real estate
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## SUUMO Japan Property Scraper

Turn public SUUMO listings into a structured dataset for Japanese rental and sale property research. Collect price in yen, layout, area, station access and photos where published, then use the rows to compare offers without copying each listing by hand.

### What you can do

- Compare advertised yen prices, floor area and layouts for Japanese property searches.
- Use station-walk information to group rental options by transport access.
- Keep SUUMO property identifiers and source links for follow-up review.
- Add published amenities, contract notes and fuller photos through optional detail collection.

### Ways to use the data

- A Tokyo relocation adviser compares rental rooms by layout, price and walk to the station.
- A housing analyst uses available rent, deposit and key-money fields to compare offers in a selected search.

### Preview of your dataset

The following is **illustrative**, using example values to show the shape of a row. They are not live listings or a guarantee that every field is present. The example prices are monthly rents; sale prices are also supported.

| Title | Price (JPY) | Area (m²) | Layout | Address |
| --- | --- | --- | --- | --- |
| Example Heights / 2階 / 1K | 85,000 | 25.5 | 1K | Example Ward, Example 1-2-3 |
| Sample Court / 3階 / 2LDK | 155,000 | 52 | 2LDK | Sample Ward, Sample 2-3-4 |
| Illustrative House / 1階 / 1DK | 98,000 | 31.2 | 1DK | Illustrative Ward, Sample 3-4-5 |

Each property row also includes its source URL when available. Fields can be missing when the site does not publish them or they cannot be parsed. Export the dataset to formats such as JSON, CSV or Excel.

### Why use this Actor

- List output separates yen price, area, layout and station-access text to support room comparisons.
- Optional detail rows can add amenities, listing dates and contract notes; the detail event replaces the list event.

Results are snapshots for your own analysis; the Actor does not itself provide ongoing monitoring or alerts.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| Property result | $5 per 1,000 results |
| Property with details | $5 per 1,000 results |

The detail event replaces the list event for the same result; the two are not added together. For example, 1,000 results at the property result rate incur $5 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Start in three steps

1. Leave the search input empty to use the default Tokyo rental search, or provide a supported public SUUMO search or listing URL.
2. Set `maxItems` to a small number and leave `scrapeDetails` off for list results, or turn it on for available detail fields. The default is 50 and the maximum is 10,000; this is a limit, not a promise of results.
3. Run the Actor, inspect the dataset and export the rows you need.

### Coverage and FAQ

**What can limit the results?** Public SUUMO search and supported detail pages are the scope. Availability of sale or rental fields depends on the page. Site availability, access restrictions, missing data and run limits can reduce the number returned. A shortened run may include a separate notice row.

**Are all fields populated?** No. Published prices, contacts and other attributes vary by listing.

**Is this live monitoring?** No. Each run captures a snapshot; schedule or compare runs in your own workflow if needed. Listings can change or disappear after collection.

This is an independent tool and is not affiliated with SUUMO.

# Changelog

This Actor's version history is a separate document: https://apify.com/stone_jadex/suumo-japan-property-scraper/changelog.md

# Actor input Schema

## `startUrls` (type: `array`):

Optional. A SUUMO search-result URL (e.g. https://suumo.jp/jj/chintai/ichiran/FR301FC001/?ar=030\&bs=040\&ta=13\&sc=13104\&pc=50\&page=1) or a detail URL (https://suumo.jp/chintai/jnc_000109707851/). Empty input uses the default Tokyo rental list from the research probe.

## `maxItems` (type: `integer`):

Stop after this many charged property rows. Alias: maxResults.

## `maxResults` (type: `integer`):

Alias for maxItems.

## `maxPages` (type: `integer`):

Optional. Each list page has up to about 50 units (pc=50).

## `startPage` (type: `integer`):

First list page when the start URL does not already set ?page=.

## `scrapeDetails` (type: `boolean`):

Adds amenities, listedAt, contract notes, and fuller photos from the public detail page. Charged as property-detail instead of property. Alias: includeDetails.

## `includeDetails` (type: `boolean`):

Alias for scrapeDetails.

## `requestDelayMs` (type: `integer`):

Default 1500 ms (slightly above the 1.2 s research gap). List pages are often slow (~8–25 s); that is site latency, not a block. A Crawl-delay in robots.txt can only raise this.

## `concurrency` (type: `integer`):

How many list or detail pages may be requested at once. Default 1 (serial). Starts are still spaced by requestDelayMs. Alias: maxConcurrency.

## `maxConcurrency` (type: `integer`):

Alias for concurrency.

## `maxRunSeconds` (type: `integer`):

Stops cleanly and writes the OUTPUT record before this limit.

## `proxyConfiguration` (type: `object`):

Direct connection by default (opt-in). Residential is a fallback only and is capped by a fixed developer budget (5 MB).

## `useProxyFallback` (type: `boolean`):

Stay on a direct connection until repeated HTTP 403 or 429, then switch to the configured proxy.

## `allowDetailOnResidential` (type: `boolean`):

Detail pages stay on a direct connection when the proxy group is residential, unless this is on. Residential download budget is a fixed developer cap (5 MB), not user-tunable.

## Actor input object example

```json
{
  "maxItems": 50,
  "startPage": 1,
  "scrapeDetails": false,
  "includeDetails": false,
  "requestDelayMs": 1500,
  "concurrency": 1,
  "maxRunSeconds": 3600,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "useProxyFallback": false,
  "allowDetailOnResidential": false
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset of public SUUMO property rows: list-tier, detail-tier and detail-failure records, plus one run-notice row when the run truncates.

## `summary` (type: `string`):

OUTPUT record with crawl statistics, seed outcomes, HTTP and robots counters, errors and the stop reason.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("stone_jadex/suumo-japan-property-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/suumo-japan-property-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call stone_jadex/suumo-japan-property-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/suumo-japan-property-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZtPd2pmNuixILFnhf/builds/3CxZ1L69UK4Z2zvci/openapi.json