Suumo Japan Scraper

Slug: fatihtahta/suumo-japan-scraper

Overview

Suumo Japan Scraper collects structured real estate listing data from Suumo.jp, including property details, pricing, location, transport access, layout, images, contact information, amenities, and listing metadata. Suumo.jp is a major Japanese real estate marketplace, making its public listing data useful for market analysis, property research, monitoring, and operational reporting. The actor turns search pages, category pages, borough result pages, and direct listing URLs into repeatable JSON output that can be used by teams and automated systems. It is designed for consistent recurring data acquisition, with configurable collection limits and optional richer listing details. The result is a dependable workflow for collecting public property data without manual browsing or copy-paste work.

Why Use This Actor

• Market research and analytics teams: build structured extraction workflows for rent, availability, geography, building type, amenities, and market movement across selected Suumo.jp result pages.
• Product and content teams: normalize property listing data for internal catalogs, map experiences, editorial review, or location-aware product features.
• Developers and data engineering teams: feed downstream systems with predictable JSON records that support ETL jobs, warehouses, search indexes, and enrichment pipelines.
• Lead generation and enrichment teams: collect public agency, contact, location, and property attributes for qualification, segmentation, and operational follow-up.
• Monitoring and competitive tracking teams: schedule repeatable collection to observe listing changes, availability signals, pricing movement, and regional coverage over time.

Common Use Cases

• Market intelligence: monitor rental supply, prices, building age, floor plans, amenities, and geographic distribution across target areas.
• Lead generation: build targeted lists of public property listings and associated real estate agencies for legitimate business workflows.
• Competitive monitoring: track changes in available listings, pricing, listing descriptions, contact details, and property presentation.
• Catalog and directory building: populate internal real estate databases with normalized public listing records.
• Data enrichment: add current public rent, address, layout, access, media, and agency attributes to CRM, BI, or analytics datasets.
• Recurring reporting: schedule periodic runs for dashboards, alerts, market snapshots, and trend analysis.

Quick Start

1. Choose one or more Suumo.jp URLs that define the listings you want to collect, such as search result, category, borough result, or direct listing URLs.
2. Set a small limit for the first validation run, such as 10 or 25.
3. Choose whether to enable enrich_data when you need expanded property details beyond standard listing fields.
4. Run the actor in Apify Console.
5. Inspect the first dataset records to confirm the output shape matches your use case.
6. Increase the limit, add more URLs, or schedule the actor after validating the dataset.

Input Parameters

The actor accepts Suumo.jp URLs, a per-URL result limit, and an enrichment option.

Parameter	Type	Description	Default
startUrls	array of strings	One or more public Suumo.jp URLs. Search, category, and borough result pages collect matching listings from that page flow; direct listing URLs collect the specific property pages provided.	–
limit	integer	Maximum number of listings to save for each input URL. Minimum value is 10.	50000
enrich_data	boolean	When enabled, records can include expanded property details such as additional amenities, summary fields, gallery images, and contact information when available. Turn it off for faster standard listing collection.	true

Choosing Inputs

Use startUrls to control collection scope. A search result or borough URL is best for collecting a market segment, while a direct listing URL is best when you already know the exact property page to collect. Broader Suumo.jp URLs improve discovery, while narrower URLs produce cleaner, more targeted datasets. Start with a small limit to validate record quality and increase it after confirming that the results match your intended geography, category, or segment. Enable enrich_data when downstream workflows need fuller property, media, feature, and contact information.

Example Inputs

Broad Discovery With A Conservative Limit

{
  "startUrls": [
    "https://suumo.jp/jj/chintai/ichiran/FR301FC001/?ar=030&bs=040&ta=12&sc=12223&cb=0.0&ct=9999999&et=9999999&cn=9999999&mb=0&mt=9999999&shkr1=03&shkr2=03&shkr3=03&shkr4=03&fw2="
  ],
  "limit": 25,
  "enrich_data": true
}

Direct Listing Collection

{
  "startUrls": [
    "https://suumo.jp/chintai/jnc_000107533873/?bc=100509695377"
  ],
  "limit": 10,
  "enrich_data": true
}

Faster Standard Listing Validation

{
  "startUrls": [
    "https://suumo.jp/jj/chintai/ichiran/FR301FC001/?ar=030&bs=040&ta=12&sc=12101&sc=12104&cb=0.0&ct=9999999&et=9999999&cn=9999999&mb=0&mt=9999999&shkr1=03&shkr2=03&shkr3=03&shkr4=03&fw2=&srch_navi=1"
  ],
  "limit": 10,
  "enrich_data": false
}

Output

Output Destination

The actor writes one JSON record per Suumo.jp property listing to the default Apify dataset. Search-only and enriched runs use the same normalized real estate contract; enrichment simply fills more nested fields when the listing detail page exposes them.

Record Envelope And Stable Identifiers

Each dataset item uses record_type = "property_listing". Use record_id as the primary deduplication key. It is built from the strongest Suumo listing identifier available, usually the unit id and then the building id. If a source id is unavailable, the public listing URL is used as the fallback.

Primary audit links and crawl context live in source_context. The public listing identity lives in entity, while listing business context, pricing, location, property facts, media, contact fields, related agency details, and source-specific attributes are grouped into their own objects.

Example Property Listing

{
  "record_type": "property_listing",
  "record_id": "100509695377",
  "source_context": {
    "source_name": "Suumo.jp",
    "source_domain": "suumo.jp",
    "source_url": "https://suumo.jp/jj/chintai/ichiran/FR301FC001/?ar=030&bs=040&ta=12&sc=12101&sc=12104",
    "listing_url": "https://suumo.jp/chintai/jnc_000107533873/?bc=100509695377",
    "canonical_url": "https://suumo.jp/chintai/jnc_000107533873/?bc=100509695377",
    "search_url": "https://suumo.jp/jj/chintai/ichiran/FR301FC001/?ar=030&bs=040&ta=12&sc=12101&sc=12104",
    "scraped_at": "2026-06-10T12:00:00.000Z",
    "detail_scraped_at": "2026-06-10T12:00:05.000Z",
    "language": "ja",
    "external_ids": {
      "building_id": "100509695377",
      "unit_id": "100509695377"
    }
  },
  "entity": {
    "title": "リブリ・都",
    "name": "リブリ・都",
    "url": "https://suumo.jp/chintai/jnc_000107533873/?bc=100509695377",
    "external_ids": {
      "building_id": "100509695377",
      "unit_id": "100509695377",
      "suumo_code": "100509695377",
      "store_code": "R01116-115069"
    }
  },
  "listing": {
    "listing_id": "100509695377",
    "listing_type": "rental",
    "transaction_type": "仲介",
    "is_new_listing": true,
    "inquiry_text": "空室状況を問い合わせる（無料）",
    "last_updated": "2026/06/10",
    "next_update": "2026/06/17"
  },
  "pricing": {
    "rent": "6.9万円",
    "management_fee": "4000円",
    "deposit": "-",
    "key_money": "6.9万円",
    "guarantee": "-",
    "amortization": "-"
  },
  "location": {
    "address": "千葉県千葉市中央区椿森２",
    "country": "Japan",
    "country_code": "JP",
    "transport_access": [
      "ＪＲ総武本線/東千葉駅 歩4分",
      "千葉都市モノレール/千葉駅 歩15分"
    ]
  },
  "property": {
    "building_id": "100509695377",
    "unit_id": "100509695377",
    "name": "リブリ・都",
    "building_name": "リブリ・都",
    "property_type": "賃貸アパート",
    "floor": "1階",
    "floor_plan": "1K",
    "floor_area": "26.08m2",
    "built": "築5年",
    "structure": "鉄骨",
    "total_floors": "1階/3階建",
    "parking": "近隣300m15000円",
    "features": ["バストイレ別", "バルコニー", "エアコン"],
    "building_meta": ["築5年", "3階建"]
  },
  "availability": {
    "move_in_date": "'26年7月上旬"
  },
  "media": {
    "main_image_url": "https://img01.suumo.com/front/gazo/fr/bukken/377/100509695377/100509695377_co.jpg",
    "building_image_url": "https://img01.suumo.com/front/gazo/fr/bukken/377/100509695377/100509695377_gw.jpg",
    "image_urls": [
      "https://img01.suumo.com/front/gazo/fr/bukken/377/100509695377/100509695377_go.jpg"
    ],
    "images": [
      {
        "url": "https://img01.suumo.com/front/gazo/fr/bukken/377/100509695377/100509695377_go.jpg",
        "alt": "建物外観",
        "number": "1"
      }
    ]
  },
  "contact_details": {
    "name": "(株)タウンハウジング千葉 稲毛店",
    "company_name": "(株)タウンハウジング千葉 稲毛店",
    "phone": "043-290-8070",
    "contact_url": "https://suumo.jp/chintai/kaisha/kc_030_175004004/"
  },
  "relationships": {
    "agency": {
      "name": "(株)タウンハウジング千葉 稲毛店",
      "phone": "043-290-8070",
      "address": "千葉県千葉市稲毛区小仲台6-1-4",
      "business_hours": "ＡＭ１０：００～ＰＭ７：００定休日： 水曜日",
      "detail_page_url": "https://suumo.jp/chintai/kaisha/kc_030_175004004/",
      "header_details": ["取引態様：仲介"],
      "tags": ["駅徒歩3分以内", "女性スタッフ"]
    }
  },
  "attributes": {
    "tags": ["動画"],
    "summary": {
      "suumo_code": "100509695377",
      "store_code": "R01116-115069",
      "layout_detail": "洋7.5 K1.7",
      "initial_costs": [
        "合計3.19万円（内訳：鍵交換代：24200円/リブリクラブ入会費:7700円）"
      ]
    },
    "description": {
      "title": "リブリ・都",
      "meta_description": "【SUUMO(スーモ)賃貸】リブリ・都...",
      "point": {
        "title": "◆築浅◆ＳＥＣＯＭ搭載！経済的な都市ガス！ネット無料！！",
        "text": "オシャレなデザイナーズ。駅すぐの生活環境良好な物件です。"
      }
    },
    "source_payloads": {
      "suumo_project_data": [
        {
          "bukkenCd": "100509695377",
          "kaisha_cd": "175004"
        }
      ]
    },
    "search_context": {
      "title": "千葉市中央区の賃貸住宅情報 検索結果",
      "total_listings": 30259
    }
  }
}

Field Reference

record_type (string, required): Stable row discriminator. Normal listing rows use property_listing.

record_id (string, required): Stable deduplication key, usually the Suumo unit id or building id.

source_context (object, optional): Source name, domain, source URL, listing URL, canonical URL, search URL, language, timestamps, and source ids.

entity (object, required): Main listing identity with title, name, url, and external_ids.

listing (object, optional): Listing type, listing id, transaction type, new-listing flag, inquiry text, and update dates.

pricing (object, optional): Displayed rent or sale price plus management fee, deposit, key money, guarantee, and amortization fields when shown.

location (object, optional): Address, Japan country context, and transport_access station/walking descriptions.

property (object, optional): Building and unit ids, property type, floor, floor plan, floor area, balcony, built/age text, structure, total floors, total units, orientation, parking, insurance, conditions, amenities, and building metadata.

availability (object, optional): Move-in date or availability timing when present.

media (object, optional): Main image URL, building image URL, image URL arrays, gallery image objects with captions/order, video URL, panorama URL, and print URL.

contact_details (object, optional): Direct public contact name, company name, phone, staff/comment text, and contact URL.

relationships.agency (object, optional): Related agency details such as name, phone, address, business hours, access, image, detail page URL, license/header details, tags, and description.

attributes (object, optional): Preservation bucket for source-specific details including tags, badges, raw normalized Suumo summary fields, descriptions, reports, floor plans, model room data, provider/action links, contact payloads, search context, and Suumo source payloads.

Data Quality, Guarantees, And Handling

• Structured records: results are normalized into predictable JSON objects for downstream use.
• Best-effort extraction: fields may vary by region, session, availability, and Suumo.jp interface changes.
• Optional fields: null-check optional fields in downstream code, especially contact, media, summary, and enriched detail fields.
• Deduplication: use property.unit_id or property.building_id when available, with url as a fallback stable key.
• Freshness: results reflect the publicly available data at run time.
• Repeated runs: use the recommended idempotency key when syncing data into warehouses, CRMs, or search indexes.

Tips For Best Results

• Start with a small limit to validate the output shape before scaling up.
• Use one geography, category, or market segment per run when you need cleaner segmentation.
• Use direct listing URLs when you need exact known properties rather than discovery.
• Use broader Suumo.jp result URLs when the goal is market coverage or discovery.
• Enable enrich_data for fuller property records, media, feature, and contact details.
• Schedule recurring runs for monitoring workflows instead of relying on manual one-off collection.
• Use stable identifiers for deduplication when storing results over time.

How To Run On Apify

1. Open the actor in Apify Console.
2. Configure the available input fields for the target scope.
3. Set the maximum number of outputs to collect with limit.
4. Click Start and wait for the run to finish.
5. Review the dataset records.
6. Download results in JSON, CSV, Excel, or other supported formats.

Scheduling & Automation

Scheduling

Automated Data Collection

You can schedule runs to keep Suumo.jp datasets fresh for reporting, monitoring, enrichment, or warehouse ingestion. Recurring schedules are useful when tracking changes in pricing, availability, and listing attributes over time.

• Navigate to Schedules in Apify Console
• Create a new schedule, such as daily, weekly, or custom cron
• Configure input parameters
• Enable notifications for run completion
• Add webhooks for automated processing

Integration Options

• BI dashboards: monitor rent, availability, property types, amenities, and geographic coverage over time.
• Data warehouses: store recurring snapshots for historical analysis, trend reporting, and market intelligence.
• CRM enrichment: sync public property and agency attributes into account, lead, or territory records.
• Google Sheets or Airtable: review smaller market samples, validate records, or coordinate lightweight operations.
• Webhooks: trigger validation, notification, or ingestion workflows after each completed run.
• Alerts and scheduled reports: notify teams when tracked listing segments change across repeated runs.

Export Formats And Downstream Use

Apify datasets can be exported or consumed by downstream systems for analytics, operations, and automated data delivery.

• JSON: for APIs, applications, and data pipelines
• CSV or Excel: for spreadsheet workflows and manual review
• API access: for automated ingestion into internal systems
• BI and warehouses: for reporting, dashboards, and historical analysis

Performance

Estimated run times:

• Small runs (< 1,000 outputs): ~3-5 minutes
• Medium runs (1,000-5,000 outputs): ~5-15 minutes
• Large runs (5,000+ outputs): ~15-30 minutes

Execution time varies based on filters, result volume, and how much information is returned per record. Highly filtered runs can finish faster, while broad discovery or detail-rich records may take longer.

Limitations

• Availability depends on what https://suumo.jp publicly exposes at run time.
• Some optional fields may be missing on sparse listings or pages with limited public data.
• Very broad searches may take longer or require a higher limit to collect the expected coverage.
• Target-side changes can affect field availability, labels, or naming.
• Regional, account, or availability differences may change visible results.
• Public listing data can change between repeated runs.

Troubleshooting

• No results returned: check that each startUrls value is a valid public Suumo.jp URL and that the page contains matching public records.
• Fewer results than expected: raise limit, use a broader source URL, or verify that Suumo.jp contains enough matching records for the selected scope.
• Some fields are empty: optional fields depend on what each listing publicly provides.
• Run takes longer than expected: reduce scope, lower limit for validation, or split broad collection into smaller segments.
• Output changed: compare the current output with the field reference and report a small sample if support is needed.

FAQ

What data does this actor collect?

It collects public Suumo.jp real estate listing data, including property identifiers, title, pricing, location, transport access, layout, images, contact information, features, descriptions, and listing context when available.

Can I filter by location, category, date, price, or other criteria?

The actor accepts Suumo.jp URLs through startUrls. Configure location, category, price, or other criteria on Suumo.jp first, then use the resulting public URL as an input.

Can I collect a specific property listing?

Yes. Add the direct Suumo.jp listing URL to startUrls and use a small limit.

Why did I receive fewer results than my limit?

The limit is a maximum, not a guarantee. The final count depends on how many matching public records are available from the provided URL and how much of that scope can be collected during the run.

Can I schedule recurring runs?

Yes. Use Apify schedules to run the actor daily, weekly, or on a custom cadence for monitoring and reporting workflows.

How do I avoid duplicates across runs?

Use property.unit_id or property.building_id when available. If those identifiers are missing, use url as a fallback key for deduplication and upserts.

Can I export the data to CSV, Excel, or JSON?

Yes. Apify datasets support exports in JSON, CSV, Excel, and other formats supported by the Apify platform.

Does this actor collect private data?

No. The actor is intended to collect publicly available information from Suumo.jp. Users are responsible for using the data lawfully and responsibly.

What should I include when reporting an issue?

Include the input used, redacted if needed, the run ID, expected behavior, actual behavior, and a small output sample when helpful.

Compliance & Ethics

Responsible Data Collection

This actor collects publicly available real estate listing information from https://suumo.jp for legitimate business purposes, including:

• Real estate research and market analysis
• Property monitoring and operational reporting
• Data enrichment for internal analytics and decision-support workflows

Users are responsible for ensuring that their use of collected data complies with applicable laws, regulations, and the target site's terms. This section is informational and not legal advice.

Best Practices

• Use collected data in accordance with applicable laws, regulations, and the target site's terms
• Respect individual privacy and personal information
• Use data responsibly and avoid disruptive or excessive collection
• Do not use this actor for spamming, harassment, or other harmful purposes
• Follow relevant data protection requirements where applicable, such as GDPR or CCPA

Support

For help, use the Issues tab or the actor page in Apify Console. Include the input used, redacted if needed, the run ID, expected versus actual behavior, and a small output sample when available. Avoid sharing secrets or sensitive data in support requests.