# Japan Investment Condo Sale Listings — Bulk (`jpmarketdata/japan-investment-condo-listings-bulk`) Actor

Collect up to 2,000 advertised Japanese used-condo sale units per run. Get asking price, area, tenant flag, source links and investment screens; optionally enrich up to 100 with disclosed monthly fees.

- **URL**: https://apify.com/jpmarketdata/japan-investment-condo-listings-bulk.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Real estate, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 used condo sale listing createds

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

## Japan Investment Condo Sale Listings — Bulk

Retrieve paginated, currently advertised used-condo sale units from Yahoo! Real Estate for investor data pipelines. Each output row is one source-grouped unit with a linked advertisement, not a market summary or a closed transaction.

### Input

Use one five-digit Japanese city or ward code. `startPage` (1–200) and `startOffset` (0–199, zero-based unit-block position) resume a prior run. With `includeDetails=false` (default), `maxPages` permits up to 40 pages and `maxItems` up to 2,000 rows. With `includeDetails=true`, request at most 5 pages and 100 rows to read monthly ownership fees. `investmentLens` may be all, tenanted\_income, compact\_rental (40 m² or less), or luxury\_price\_band (asking price at least JPY 100 million). The lenses are mechanical filters and are not recommendations. Source ordering can change across runs, so resuming cannot guarantee a stable full inventory snapshot.

### Output

One dataset row per deduplicated advertised unit carries the asking price in JPY, area and asking price per m², building and layout facts, the source's tenant-in-place marker, and source search and selected advertisement URLs. Detail mode adds disclosed monthly management and repair-reserve fees; a monthly total appears only when both are present. Unavailable components are omitted. `feeDisclosure=not_requested` identifies bulk list rows. Each row repeats nextPage, nextOffset and truncated for resuming; nextPage=0 means the observed source pagination ended. Advertised asking prices are not sale transactions or appraisals. No rental income, taxes, purchase costs, vacancy data or yield estimates are supplied.

### Pricing

Provisional PPE hypothesis pending owner pricing decision: $0.005 per emitted `condo-listing-created` row, charged with its dataset push if released at that price. A unit skipped because its detail vanished, source failure, or an empty segment produces no charged row. Under this unapproved price, bulk mode's 2,000-row cap would cost $10.00 and detail mode's 100-row cap would cost $0.50 per run.

### Limits

Bulk list mode reads at most 40 public search pages and no details. Detail mode reads at most 5 search pages and one public detail per selected unit. A hard cap of 110 HTTP requests and 300 seconds applies. Starts are spaced by at least 1.5 seconds. Responses are size-bounded and parsed incrementally in 256 MB without a browser, proxy, login, paid API or persistent source cache. The Actor stops on authentication, rate-limit, timeout and structure failures instead of reporting partial coverage as complete. A zero-result requested window fails with a clear reason. Detail-page datacenter access still requires a release probe.

### Privacy

The output excludes agent and seller identities, names of contact staff, phone numbers, business contacts, comments, photos, image URLs and inquiry links even if the source page contains them. Only public sale attributes and source page URLs are kept. This Actor is independent of Yahoo! Real Estate and reads public pages on demand.

# Actor input Schema

## `cityCode` (type: `string`):

One 5-digit Japanese city or ward code, such as 13113 for Shibuya. Only Yahoo! Real Estate used-condo for-sale results are read.

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

One-based Yahoo! Real Estate result page. Use nextPage from the previous run to continue. Source ordering can change between runs.

## `startOffset` (type: `integer`):

Zero-based position among unit blocks on startPage. Use nextOffset from the previous run; 0 starts at the first unit.

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

Read at most 1 to 40 result pages in bulk list mode. Detail mode permits at most 5 pages. Advertised units per page vary.

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

Output at most 1 to 2,000 deduplicated sale units in bulk list mode, or 100 with details. When the limit falls mid-page, nextPage and nextOffset point to the first unprocessed unit block.

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

Off by default for high-volume list extraction. When true, read each selected advertisement detail for management and repair reserve fees; requires maxItems at most 100 and maxPages at most 5.

## `investmentLens` (type: `string`):

Choose all, tenanted\_income (source says rented out), compact\_rental (area at most 40 m2), or luxury\_price\_band (asking price at least JPY 100 million). These are labels, not returns or recommendations.

## Actor input object example

```json
{
  "cityCode": "13113",
  "startPage": 1,
  "startOffset": 0,
  "maxPages": 10,
  "maxItems": 500,
  "includeDetails": false,
  "investmentLens": "all"
}
```

# Actor output Schema

## `listings` (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 = {
    "cityCode": "13113"
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/japan-investment-condo-listings-bulk").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 = { "cityCode": "13113" }

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/japan-investment-condo-listings-bulk").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 '{
  "cityCode": "13113"
}' |
apify call jpmarketdata/japan-investment-condo-listings-bulk --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/japan-investment-condo-listings-bulk"
        }
    }
}
```

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/ZvDp482fRoMfjS3DQ/builds/IYa7fXN3tmFXvagU1/openapi.json