# Japan Official Land Price History Bulk (`jpmarketdata/japan-official-land-price-history-bulk`) Actor

Export official Japan posted land-price histories for 2026 reference sites, with annual JPY/m² observations, selection flags, prefecture shards and source attribution.

- **URL**: https://apify.com/jpmarketdata/japan-official-land-price-history-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

$50.00 / 1,000 land price history chunk exporteds

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 Official Land Price History Bulk

Export annual posted land-price histories from Japan MLIT's official 2026 L01 CSV archive. This is a bulk dataset for analysts, not a listing, transaction, rental, yield or investment product. The source year is fixed at 2026.

### Input

Choose current prefecture code `01`-`47` or `ALL`, an observation-year window within 1983-2026, zero-based `pointOffset`, and `maxPoints` from 1 to 2,000. The default is Tokyo, 2016-2026, offset 0, 1,000 sites. The offset counts sites with at least one price observation in the selected year window. Continue at `nextPointOffset` while `truncated` is true. Pass the first shard's `sourceSha256` as `expectedSourceSha256` on later shards so a revised official ZIP cannot silently change the offset order.

### Output

Each dataset row is one site present in the 2026 snapshot, with annual price observations in JPY per square meter, selection-status code and full attribute-change code. Rows also carry the current point code, source year, license, attribution, ZIP SHA-256 and shard metadata: scope, matched count, returned count, next offset and truncation. The historical series excludes sites retired before 2026; identifiers, selection and site attributes can change. A price of `0` or `_` is omitted as a missing observation, even when the year is selected; an unselected year with a nonzero price is a source error. If no valid observations remain in the selected scope, the run fails. Current attributes are not imputed to earlier years. The dataset is a cohort history, not a full historical nationwide cross-section or a parcel valuation.

### Pricing

Provisional PPE hypothesis: $0.05 for each successfully delivered chunk of up to 1,000 site-history dataset rows, including a final smaller chunk. Source validation errors and empty results carry no event charge; chunks already delivered and charged remain billed if a later dataset push fails. A run is limited to 2,000 rows, so at most two chargeable chunks. This price requires owner confirmation before publication.

### Limits

One anonymous official nationwide ZIP GET per run; no third-party API key, browser or proxy. The Actor caps compressed input at 8 MiB, uncompressed CSV at 64 MiB, HTTP wait at 30 seconds, memory at 256 MB and run time at 300 seconds. It validates the ZIP, CSV headers and selected 2026 cohort and fails for invalid offsets, malformed source data, authorization failure, rate limiting, timeout or unexpectedly zero sites. The source CSV order is stable only while `sourceSha256` matches.

### Privacy

Only official public price, year, point-code and continuity fields are returned. Street address, owner, name, email and device data are excluded. Source: MLIT Japan National Land Numerical Information L01 land price data, 2026, https://nlftp.mlit.go.jp/ksj/gml/datalist/KsjTmplt-L01-2026.html ; processed by jpmarketdata. The 2026 archive is CC BY 4.0; original source precision and continuity limitations pass through to users. MLIT does not endorse this Actor.

# Actor input Schema

## `prefectureCode` (type: `string`):

Two-digit current prefecture code 01-47, or ALL for the nationwide 2026 reference-site cohort.

## `startYear` (type: `integer`):

First annual posted-price observation to include from the 2026 L01 archive; 1983-2026.

## `endYear` (type: `integer`):

Last annual posted-price observation to include, no later than the 2026 archive year.

## `pointOffset` (type: `integer`):

Zero-based offset among 2026 sites with a price in the selected years and prefecture, in fixed source CSV order. Use nextPointOffset from the previous shard.

## `maxPoints` (type: `integer`):

Return at most 2,000 site-history rows in this shard; use ALL with successive offsets for a nationwide export.

## `expectedSourceSha256` (type: `string`):

Optional SHA-256 from an earlier shard. If supplied, fail when MLIT has revised the ZIP so offsets could shift.

## Actor input object example

```json
{
  "prefectureCode": "13",
  "startYear": 2016,
  "endYear": 2026,
  "pointOffset": 0,
  "maxPoints": 1000,
  "expectedSourceSha256": ""
}
```

# Actor output Schema

## `siteHistories` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/japan-official-land-price-history-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/japan-official-land-price-history-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 '{}' |
apify call jpmarketdata/japan-official-land-price-history-bulk --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/japan-official-land-price-history-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/eB7Ohwzb0UX8xf2rT/builds/7UFfyZJ7MqInq0Ssd/openapi.json