at home Scraper — Japan Rental Property Data & API 🏯

🎉 Turn a top Japan rental portal into clean, structured data — one row per room, geo-located, ready for analysis

For real-estate analysts, investors, relocation agents, and data teams working the Japanese rental market

---

📋 Overview

Need Japanese rental listings as clean data instead of endless scrolling? This scraper turns at home (athome.co.jp) search results into structured JSON/CSV — and it does the one thing most Japan property tools get wrong: it gives you one clean row per room with the data buyers actually need — price in JPY, latitude/longitude geo, agent contact details, deposit/key-money breakdown, and grouped facility lists.

Why analysts and agencies choose us:

• ✅ Per-room rows: every rentable unit becomes one clean record — no nested mess
• ⚡ Fast & lightweight: direct extraction, no slow headless browser, no proxy overhead
• 🗺️ GPS coordinates included: real latitude/longitude on every detail listing — map and cluster instantly
• 📞 Agent contacts: agency name, address, phone and license number — built-in lead data
• 🎯 45+ data points: rent (normalised to JPY), 万円 raw text, layout, area, floor, deposit, key money, building age, station access, facilities, photos
• 💴 Pay-per-result: only pay for listings you actually receive — transparent and cheap
• 💎 Two depths: fast overview for whole-market sweeps, full detail for JSON-LD + spec table
• ✨ Three ways in: by prefecture slug, by pasted search URL (keeps every filter), or by listing URL

---

✨ Features

• 🏢 Rental listings, done right — one record per rentable room
• 💴 Money normalised — 11.9万円 becomes 119000 JPY and keeps the original string
• 📐 Rent-per-m² built in — yield and comparison math ready out of the box
• 🗺️ Geo lat/long — every detail listing carries real coordinates for mapping
• 🚉 Station access — every line / station / walk-time entry captured
• 📞 Agent block — agency name, address, phone, license number
• 🛁 Facility groups — bath/toilet, kitchen, security, storage, equipment, TV/comms
• 🔎 Detail enrichment — deposit, key money, guarantor, renewal fee, contract period, parking, pets, full photo set
• 🔗 Paste-a-URL mode — apply filters on the site, paste the link, every filter is preserved
• 📦 Clean exports — JSON, CSV, Excel straight from the dataset

---

🎬 Quick Start

Pick a mode, give it a prefecture slug or a search URL, and run. Listings stream into your dataset as clean rows. Export as JSON, CSV, or Excel.

curl -X POST https://api.apify.com/v2/acts/sian.agency~athome-property-scraper/runs?token=YOUR_TOKEN \
-H 'Content-Type: application/json' \
-d '{"scrapeMode": "overview", "searchMode": "byPlace", "places": ["tokyo"]}'

---

🚀 Getting Started (3 Simple Steps)

Step 1: Choose your input

Enter a prefecture slug (e.g. tokyo), paste a search URL, or list specific listing URLs.

Step 2: Pick depth

overview for fast whole-market room cards, or detail for the full JSON-LD + spec table (geo, agent, facilities).

Step 3: Run & export

Start the run and download your results as JSON, CSV, or Excel.

That's it! In under a minute, you'll have:

• A clean, per-room dataset
• Rent normalised to JPY plus the raw 万円 strings
• Layout, area, floor, geo coordinates, deposit, station access, agent contacts, and photos

---

📥 Input Configuration

Field	Type	Required	Description
scrapeMode	string	No	overview (fast room cards) or detail (full JSON-LD + spec table)
searchMode	string	No	byPlace, bySearchUrl, or byListingUrl
places	array	No	Prefecture slugs, e.g. ["tokyo"]
wards	array	No	Optional ward/city slugs paired with places, e.g. ["shinjuku-city"]
searchUrls	array	No	Pasted search URLs (path-segment filters preserved)
listingUrls	array	No	Detail URLs or listing codes (detail mode)
filters	array	No	Extra path-segment filters, e.g. 1ldk, pet, walk10
maxResults	integer	No	Max listings per run (FREE: 25, PAID: unlimited)

Example — overview by prefecture:

{
  "scrapeMode": "overview",
  "searchMode": "byPlace",
  "places": ["tokyo"],
  "wards": ["shinjuku-city"],
  "maxResults": 200
}

Example — detail by search URL:

{
  "scrapeMode": "detail",
  "searchMode": "bySearchUrl",
  "searchUrls": ["https://www.athome.co.jp/chintai/tokyo/shinjuku-city/1ldk/list/"]
}

---

📤 Output

Results are saved to the Apify dataset with 45+ fields per listing, including:

Field	Type	Description
listingId	string	athome listing code (物件番号)
url	string	Canonical listing URL
price	number	Monthly rent in JPY
price_text	string	Raw 11.9万円 string
price_per_sqm_jpy	number	Computed rent per m²
layout	string	間取り, e.g. 1K, 2LDK
floor_size_sqm	number	面積 in m²
floor / floors_total	number	Room floor / building floors
deposit / key_money	string	敷金 / 礼金
build_year / build_age	number / string	Build year / 築年月
latitude / longitude	number	GPS coordinates (detail mode)
address / region / locality	string	住所 / 都道府県 / 市区町村
transit	array	Line / station / walk-time entries
agent_name / agent_phone / agent_license	string	Listing agency details
bath_toilet / kitchen / security / storage	array	Grouped facility lists
images	array	Photo URLs

Example:

{
  "listingId": "6990708422",
  "url": "https://www.athome.co.jp/chintai/6990708422/",
  "propertyTitle": "Ｎ’ｓ高田馬場",
  "price": 119000,
  "price_text": "11.9万円",
  "price_per_sqm_jpy": 3955,
  "layout": "1K",
  "floor_size_sqm": 30.09,
  "floor": 4,
  "floors_total": 9,
  "deposit": "1ヶ月",
  "mgmt_fee": "15,000円",
  "build_year": 2019,
  "latitude": 35.7159442,
  "longitude": 139.6975817,
  "region": "東京都",
  "transit": ["ＪＲ山手線 / 高田馬場駅 徒歩10分"],
  "agent_name": "TKホーム(有)東和企画",
  "agent_phone": "+81-3-5332-6155",
  "image_count": 16
}

---

💼 Use Cases & Examples

1. Rental Market Research

Analysts mapping rent-by-area across a prefecture. Input: prefecture slug · Output: per-room dataset with price & m² · Use: build a rent heatmap by ward and station.

2. Property Investment Analysis

Investors comparing yields across buildings. Input: a filtered search URL · Output: rent-per-m² on every unit · Use: rank candidate buildings by gross yield.

3. Relocation & Tenant Search

Relocation agents shortlisting homes for clients. Input: prefecture + layout/budget filters · Output: clean rows with deposit, key money, station walk-time · Use: hand clients a tidy comparison sheet.

4. Real-Estate Lead Generation

Agencies building prospect lists of active listings + agents. Input: broad search by area · Output: building, address, layout, agent phone & license · Use: feed CRM pipelines.

5. Mapping & Geo Analysis

Data teams plotting inventory on a map. Input: detail mode over a search · Output: latitude/longitude on every listing · Use: cluster, geofence, and visualise.

6. Academic & Policy Research

Researchers studying Japanese housing markets. Input: multiple prefectures · Output: structured, reproducible datasets · Use: quantitative housing studies.

---

🔗 Integration Examples

JavaScript/Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });

const run = await client.actor('sian.agency/athome-property-scraper').call({
  scrapeMode: 'overview', searchMode: 'byPlace', places: ['tokyo']
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')

run = client.actor('sian.agency/athome-property-scraper').call(
    run_input={'scrapeMode': 'overview', 'searchMode': 'byPlace', 'places': ['tokyo']}
)

for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

cURL

curl -X POST 'https://api.apify.com/v2/acts/sian.agency~athome-property-scraper/runs?token=YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"scrapeMode": "overview", "searchMode": "byPlace", "places": ["tokyo"]}'

Automation Workflows (N8N / Zapier / Make)

1. Trigger: Schedule or webhook
2. HTTP Request: Call the actor API
3. Process: Handle the JSON results
4. Action: Save to a sheet, notify, or sync to CRM

---

📊 Performance & Pricing

FREE Tier (Try It Now)

• 25 listings per run — full feature access, same quality
• No credit card required
• Perfect for testing and small projects

PAID Tier (Production Ready)

• Unlimited listings per run
• Pay-per-result: only charged for listings you actually receive

💴 Cheap by design — direct extraction with no proxy overhead keeps the per-listing price among the lowest for Japanese real-estate data.

🔗 View current pricing

---

❓ Frequently Asked Questions

Q: How many listings can I scrape? A: FREE tier: 25 per run. PAID tier: unlimited.

Q: Do I need an account or API key for the source site? A: No. Just provide a prefecture slug or a search URL.

Q: Are GPS coordinates included? A: Yes — detail-mode listings carry real latitude/longitude, plus address, region, locality and station access.

Q: What output formats are available? A: JSON, CSV, and Excel — export directly from the Apify dataset.

Q: What's the difference between overview and detail? A: Overview is the fast room-card data. Detail fetches each listing's full page (JSON-LD + spec table) for geo, agent contacts, deposit/key-money breakdown, facilities and the full photo set, then merges them into one record.

Q: How do I filter precisely? A: Apply your filters on the site's search UI, then paste the resulting URL in searchUrls — every path-segment filter is preserved. Or add slugs like 1ldk, pet, walk10 in filters.

---

🐛 Troubleshooting

No results returned

• Check the prefecture slug (e.g. tokyo) or that the pasted URL is a /chintai/.../list/ search page.

Fewer rows than expected

• FREE tier caps at 25 listings per run — upgrade for unlimited.
• Narrow filters may simply return fewer listings.

A specific listing failed in detail mode

• The listing may have expired or been delisted; the run continues and skips it.

---

⚖️ Is it legal to scrape data?

Our actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our actors, when used for ethical purposes by Apify users, are safe.

However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

You can also read Apify's blog post on the legality of web scraping.

Disclaimer: This is an independent tool and is not affiliated with, endorsed by, or sponsored by at home Co., Ltd. "at home" (アットホーム) and athome.co.jp are trademarks of their respective owners. Use this actor in compliance with the source site's terms of service and all applicable laws.

---

🤝 Support

Join our active support community

• For issues or questions, open an issue in the actor's repository
• Check the SIÁN Agency Store for more automation tools
• 📧 apify@sian-agency.online

---

Built by SIÁN Agency | More Tools