# SUUMO Rental Scraper (Japan) (`barefoot_grade/suumo-jp-scraper`) Actor

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.

- **URL**: https://apify.com/barefoot\_grade/suumo-jp-scraper.md
- **Developed by:** [Philip Kirkbride](https://apify.com/barefoot_grade) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 results

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 Rental Scraper (Japan)

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):

| field | notes |
|---|---|
| `listing_key` | stable composite key `suumo.jp:{prefecture}:{url}\|{layout}\|{area}\|{rent}` — dedupe on this |
| `url` | room 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_jpy` | monthly rent normalized from 万円 (`8.3万円` → 83000) |
| `management_fee_jpy` | 管理費 in JPY when quoted |
| `nearest_station` / `walk_min` | station from 交通 (slash form `ＪＲ中央線/八王子駅`) and `歩N分` / `徒歩N分` on the nearest line (null on bus-only lines) |
| `images` | cassette image URLs (lazy-load placeholders excluded) |
| `prefecture` / `prefecture_code` / `source` / `scraped_at` | request scope + provenance |

### Example input

```json
{"prefecture": "13", "maxPages": 2, "maxResults": 100}
```

```json
{"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.

# Actor input Schema

## `prefecture` (type: `string`):

Japanese prefecture to search. Each maps to the site's JIS prefecture code (ta) and its parent region (ar) by construction; v1 covers the four probe-verified Kanto prefectures (ta 11/12/13/14).

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

Result pages to fetch (50 entries per page).

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

Stop after this many room adverts.

## `requestDelaySecs` (type: `number`):

Minimum 0.5 seconds.

## Actor input object example

```json
{
  "prefecture": "13",
  "maxPages": 1,
  "maxResults": 50,
  "requestDelaySecs": 1
}
```

# Actor output Schema

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

No description

# 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 = {
    "prefecture": "13",
    "maxPages": 1,
    "maxResults": 50,
    "requestDelaySecs": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("barefoot_grade/suumo-jp-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 = {
    "prefecture": "13",
    "maxPages": 1,
    "maxResults": 50,
    "requestDelaySecs": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("barefoot_grade/suumo-jp-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 '{
  "prefecture": "13",
  "maxPages": 1,
  "maxResults": 50,
  "requestDelaySecs": 1
}' |
apify call barefoot_grade/suumo-jp-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,barefoot_grade/suumo-jp-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/w7buirFcBZijVLv2T/builds/kATWomA3aL3SdF9Ra/openapi.json