# Yahoo! Real Estate Japan Rent Scraper (Yahoo!不動産 賃貸) (`ardent_fork/yahoo-realestate-japan-rent`) Actor

Rental listings from realestate.yahoo.co.jp (Yahoo!不動産) by city: rent, fees, deposit, key money, layout, m², floor, building age, stations, address, coordinates, agent. Japan's largest open rental aggregator. No login, no API key.

- **URL**: https://apify.com/ardent_fork/yahoo-realestate-japan-rent.md
- **Developed by:** [KF P](https://apify.com/ardent_fork) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 listings

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

## Yahoo! Real Estate Japan Rent Scraper (Yahoo!不動産 賃貸)

Scrape rental listings (賃貸マンション・アパート・一戸建て) from [Yahoo!不動産](https://realestate.yahoo.co.jp/rent/), Japan's largest open rental aggregator: it republishes listings from SUUMO, LIFULL HOME'S, athome and hundreds of agents, so one crawl covers the market. Every result is one room with rent, management fee, deposit and key money in yen, layout, floor area in m², floor, building age, nearest stations with walking minutes, address and coordinates, and (with details) direction, contract period, move-in date, listing date, remarks and the listing agent.

Pick cities by JIS code or paste a search URL from the site. No login, no API key, no browser.

### Input

| Field | Type | Description |
|---|---|---|
| `areas` | array | Cities as `"<prefectureCode>/<cityCode>"` (JIS codes, e.g. `13/13101` 東京都千代田区, `13/13113` 渋谷区, `27/27127` 大阪市北区) or a full `https://realestate.yahoo.co.jp/rent/search/03/<pref>/<city>/` URL copied from the site (max 50). Listings come in the site's default order, newest first. |
| `detailUrls` | array | Specific `https://realestate.yahoo.co.jp/rent/detail/<id>/` URLs (max 2000). |
| `fetchDetails` | boolean | Open each listing page for direction, contract period, move-in, listing date, remarks, facilities and the agent (default `true`; one extra request per listing). `false` = list-level fields only, about 30× faster. |
| `maxItems` | integer | Stop after this many listings (default 100, max 20000). You pay only for pushed listings. |
| `maxConcurrency` | integer | Parallel requests (default 5, max 10). Requests are spaced ~1 s apart, so throughput is about one page per second regardless. |
| `proxyConfiguration` | object | Optional proxy settings; normally not needed. |

At least one of `areas` / `detailUrls` is required. City codes: the site's own URLs carry them (`/rent/search/03/13/13113/` → `13/13113`); any JIS 市区町村コード table works too.

```json
{
  "areas": ["13/13101", "13/13113"],
  "fetchDetails": true,
  "maxItems": 500
}
```

### Output

One dataset item per room:

```json
{
  "id": "_0000008657270c4b103669fbce7203c08d54d52b48b5",
  "url": "https://realestate.yahoo.co.jp/rent/detail/_0000008657270c4b103669fbce7203c08d54d52b48b5/",
  "area": "13/13101",
  "buildingName": null,
  "buildingLabel": "山手線 神田駅 8階建 築24年",
  "kind": "マンション",
  "prefecture": "東京都",
  "city": "千代田区",
  "cityCode": "13101",
  "address": "東京都千代田区神田多町2",
  "lat": 35.69425271,
  "lng": 139.76928534,
  "rent": 120000,
  "managementFee": 0,
  "keyMoney": 240000,
  "securityDeposit": 0,
  "deposit": 0,
  "cancellationDeduction": 0,
  "layoutCode": 2,
  "layout": "1K",
  "layoutDetail": "1K (洋7.5 K2.0)",
  "areaSqm": 23.44,
  "floor": 8,
  "totalFloors": 8,
  "builtOn": "2002-11",
  "yearsOld": 24,
  "isNewlyBuilt": false,
  "isNewArrival": true,
  "direction": "南東",
  "contractPeriod": "2年",
  "buildCondition": "定期借家",
  "insurance": "あり",
  "moveIn": "相談",
  "listedAt": "2026-10-09",
  "remark": "合計3.3万円(内訳：鍵交換代3.3万円)\n更新料　新賃料1.00ヶ月分\n…",
  "prComment": "【神田駅から徒歩3分】…",
  "facilities": ["015", "018", "023"],
  "features": ["ac", "al", "bd", "ev", "sk"],
  "stations": [
    { "line": "山手線", "station": "神田", "walkMinutes": 4, "label": "神田駅/山手線 徒歩4分" },
    { "line": "東京メトロ丸ノ内線", "station": "淡路町", "walkMinutes": 5, "label": "淡路町駅/東京メトロ丸ノ内線 徒歩5分" }
  ],
  "imageUrl": "https://realestate-pctr.c.yimg.jp/…",
  "layoutImageUrl": "https://realestate-pctr.c.yimg.jp/…",
  "agent": { "name": "REOL(株)新宿駅前店", "transactionType": "仲介", "address": "東京都新宿区西新宿1-15-4…", "license": "東京都知事(1)第108035号 / …", "tel": "03-5909-3670" },
  "detailsFetched": true
}
```

All money fields are yen per month (rent, management fee) or one-off yen (deposit, key money, security deposit, cancellation deduction); `0` means the site shows なし (none), `null` means not stated. `buildingName` is set only when the agent allows the name to be shown; `buildingLabel` is the site's own label (line, station, floors, age). `layout` is the standard label (ワンルーム, 1K, 1LDK, 2LDK …); `layoutDetail` adds the room breakdown when details were fetched. `features` are the site's amenity codes (`al` auto-lock, `ev` elevator, `bt` bath/toilet separate, `ac` air conditioning …) and `facilities` its numeric facility codes.

With `fetchDetails: false` the record carries the list-level fields only and `detailsFetched` is `false`.

### Notes

- Listings are taken in the site's default order (newest first). Sorted or map-bounded searches are not offered: the site's robots.txt excludes those URL forms, and this actor honours it.
- `maxItems` counts rooms, not buildings; a building with several vacant rooms yields several records.
- A wrong city code answers 404 and is reported in the run's status message; other areas in the same run continue.
- An item is pushed and charged exactly once; re-running a migrated or resumed run never double-charges.
- Only rentals (賃貸) are covered. Sale listings (中古マンション, 新築 etc.) are a different vertical with different URL rules.

### Speed, cost and timeouts

Requests are paced at about one per second to stay within the site's comfort zone. With `fetchDetails: true` that is roughly 50 listings per minute (one list page per 56 rooms plus one page per room); with `fetchDetails: false` about 3,000 listings per minute. The default run (one city, 100 listings with details) finishes in about 2 minutes. For a whole prefecture, raise the run timeout or split the cities across runs; the run stops cleanly at `maxItems` or at your budget limit and everything pushed up to that point is kept.

### Use cases

- Rent indices and market analytics for Tokyo 23 wards, Osaka, Nagoya, Fukuoka: price per m² by layout, age and station distance.
- Relocation and foreign-tenant agencies: fresh inventory by city with fees broken out (deposit, key money, management fee).
- Investors tracking asking rents for specific buildings or areas over time.
- Proptech and data teams needing a structured feed of Japanese rental listings without building scrapers for each portal.

# Actor input Schema

## `areas` (type: `array`):

Areas to crawl as "<prefectureCode>/<cityCode>" (JIS codes: 13/13101 = 東京都千代田区, 13/13113 = 渋谷区, 27/27127 = 大阪市北区) or a full https://realestate.yahoo.co.jp/rent/search/03/<pref>/<city>/ URL copied from the site (max 50). Listings are taken in the site's default order, newest first.

## `detailUrls` (type: `array`):

Specific listings to fetch: https://realestate.yahoo.co.jp/rent/detail/<id>/ URLs (max 2000).

## `fetchDetails` (type: `boolean`):

Open each listing's page for direction, contract period, move-in date, listing date, remarks, facilities and the agent. One extra request per listing (~1 s each). Off = list-level fields only, much faster.

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

Stop after this many listings have been pushed (1–20000). You are only charged for pushed listings.

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

Parallel requests (1–10). Requests are additionally spaced ~1 s apart, so throughput is about one page per second regardless.

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

Proxy settings. The site answers datacenter IPs fine; leave empty unless you see blocks.

## Actor input object example

```json
{
  "areas": [
    "13/13101",
    "https://realestate.yahoo.co.jp/rent/search/03/13/13113/"
  ],
  "detailUrls": [
    "https://realestate.yahoo.co.jp/rent/detail/_000004304633d8bd94b2ad0a58b479d4e182d310dafc/"
  ],
  "fetchDetails": true,
  "maxItems": 100,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `listings` (type: `string`):

Dataset items, one per room (rent, fees, layout, area, floor, building, stations, address, agent).

# 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 = {
    "areas": [
        "13/13101"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ardent_fork/yahoo-realestate-japan-rent").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 = { "areas": ["13/13101"] }

# Run the Actor and wait for it to finish
run = client.actor("ardent_fork/yahoo-realestate-japan-rent").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 '{
  "areas": [
    "13/13101"
  ]
}' |
apify call ardent_fork/yahoo-realestate-japan-rent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ardent_fork/yahoo-realestate-japan-rent"
        }
    }
}
```

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/hbDcuW5qRAOeneDLL/builds/KCzwHChvX1EQAIjps/openapi.json