# Korea Commercial Property Sales - Official Transaction Register (`loopchips/korea-commercial-trades`) Actor

Every reported sale of retail, office, hospitality and other commercial property in Korea, straight from the government register. Price, building and land area, zoning, use class, buyer and seller type, with price per pyeong calculated. Search by district name instead of hunting for codes.

- **URL**: https://apify.com/loopchips/korea-commercial-trades.md
- **Developed by:** [Loopchips](https://apify.com/loopchips) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 transactions

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Korea Commercial Property Sales - Official Transaction Register

Every reported sale of retail, office, hospitality and other commercial property
in Korea, straight from the government register.

When commercial property changes hands in Korea the sale must be reported by law,
and the Ministry of Land publishes those filings. This Actor turns them into clean
rows: price, building and land area, zoning, use class, buyer and seller type,
with price per pyeong worked out for you.

This is the commercial counterpart to apartment data. It covers the buildings
apartments never do - shops, offices, hotels, clinics and mixed-use blocks.

### What you get

| Field | Description |
|---|---|
| `dealDate` | Date of the contract |
| `district` / `legalDong` | District and neighbourhood |
| `buildingUse` | Use class: 판매 retail, 업무 office, 숙박 hospitality, 근린생활 neighbourhood facility |
| `landUse` | Zoning: 일반상업, 중심상업, 준주거, 제1~3종일반주거 and so on |
| `buildingType` / `isWholeBuilding` | 집합 a unit inside a building, 일반 the whole standalone building |
| `priceManwon` / `priceKrw` | Price as published, and in won |
| `buildingAreaM2` / `buildingAreaPyeong` | Building area, both units |
| `pricePerPyeongManwon` | How the Korean market actually quotes value |
| `landAreaM2` / `landAreaPyeong` | Land area, filled in for standalone buildings |
| `landPricePerPyeongManwon` | Price against land area, the figure that drives redevelopment |
| `floor` / `buildYear` / `buildingAgeYears` | Floor, year built, and age at the time of sale |
| `dealType` / `isDirectDeal` | Brokered or direct - close to half of these deals skip an agent |
| `buyerType` / `sellerType` | Individual, corporate or public body |
| `isShareDeal` | Whether only a fraction of the property was sold |
| `isCancelled` / `cancelledOn` | Contracts later cancelled |

### You need your own free key

This Actor calls the government API on your behalf, using a key issued to you.

1. Sign up at data.go.kr
2. Search for 상업업무용 부동산 매매 실거래가 자료
3. Press 활용신청 - approval is automatic and gives 10,000 calls a day
4. Paste the Encoding key into this Actor

The data itself is published with no usage restrictions, so what you collect is
yours to keep, analyse and redistribute.

### Example input

```json
{
  "serviceKey": "your-key-here",
  "districts": ["서울 강남구", "서울 종로구"],
  "startMonth": "202601",
  "endMonth": "202606",
  "buildingTypes": ["판매", "업무"]
}
```

### District names

You can write a district name such as `서울 강남구`, or just `강남구`. Names are
resolved for Seoul and the metropolitan cities. Everywhere else, use the
five-digit code, which always works - for example `41135` for 성남시 분당구.

Codes are the first five digits of the legal district code.

### Example output

```json
{
  "dealDate": "2026-06-28",
  "district": "종로구",
  "legalDong": "안국동",
  "buildingType": "일반",
  "isWholeBuilding": true,
  "buildingUse": "제2종근린생활",
  "landUse": "제1종일반주거",
  "priceManwon": 900000,
  "priceKrw": 9000000000,
  "buildingAreaM2": 468.11,
  "buildingAreaPyeong": 141.6,
  "pricePerPyeongManwon": 6356,
  "landAreaM2": 238,
  "landAreaPyeong": 71.99,
  "landPricePerPyeongManwon": 12502,
  "buildYear": 2019,
  "buildingAgeYears": 7,
  "dealType": "중개거래",
  "isDirectDeal": false,
  "buyerType": "법인",
  "sellerType": "법인"
}
```

### What people use it for

- **Site selection** - what retail space actually costs on a given street,
  filtered to the use class you need
- **Valuation and lending** - comparable commercial sales by zoning and area
- **Redevelopment screening** - land price per pyeong on standalone buildings
- **Corporate activity** - which districts corporate buyers are moving into
- **Proptech products** - a legal, citable source you can build on

### Reading the data honestly

Four things distort commercial figures if you ignore them. This Actor handles
the first three for you, and gives you the fields to catch the fourth.

**Part-share deals.** About one deal in fourteen transfers only a fraction of a
property. The price on that row does not correspond to the area on the same row,
so a 20% share reads as an implausible bargain. Those rows are kept and flagged
with `isShareDeal`, and their per-pyeong figures are left empty rather than
published as a number that would mislead. Set `excludeShareDeals` to drop them.

**Unit versus whole building.** A 집합 row is one unit inside a building; a 일반
row is the entire standalone building. Mixing them makes averages meaningless.
Use `isWholeBuilding` to separate them. Land area and floor are only ever filled
in for standalone buildings, which is why those fields are often empty.

**Cancelled contracts.** Excluded by default so averages are not distorted. Turn
them on if you want to study cancellations.

**Bulk registrations from a single development.** Commercial buildings are often
sold unit by unit and registered in the same month, so one new development can
supply most of a district's rows. In a June 2026 sample of 종로구, 89 of 129 unit
sales came from one building on a single lot, pulling the district median well
above the surrounding market. Group by `legalDong` and `jibun` before taking an
average, or weight by floor area.

### Pricing

Pay per result. You are charged only for transactions actually returned.

### Notes

- Prices are published in 만원 (ten thousand won). Both that and the won figure
  are included.
- `jibun` is partly masked at source on commercial records, so it identifies the
  block rather than the exact lot.
- `agentDistrict` is where the broker is registered, which is not always where
  the property is.
- Source: Ministry of Land, Infrastructure and Transport, via data.go.kr.
  Updated daily.

# Actor input Schema

## `serviceKey` (type: `string`):

Your own free key from data.go.kr. Search for 상업업무용 부동산 매매 실거래가 자료 and press 활용신청 - approval is automatic and gives 10,000 calls a day. Paste the Encoding key.

## `districts` (type: `array`):

District names such as "서울 강남구" or "강남구", or five-digit codes such as 11680. Names are resolved for you.

## `startMonth` (type: `string`):

YYYYMM, for example 202601. Defaults to the current month.

## `endMonth` (type: `string`):

YYYYMM. Defaults to the start month, so leaving both empty returns this month only.

## `buildingTypes` (type: `array`):

Keep only these 건물주용도 values, for example 판매 for retail or 업무 for office. Leave empty for every use class.

## `includeCancelled` (type: `boolean`):

Cancelled contracts are excluded by default so averages are not distorted.

## `excludeShareDeals` (type: `boolean`):

A 지분 deal sells a fraction of a property, so its price does not match the area on the same row. They are kept by default and flagged, with per-pyeong figures left empty.

## `requestDelayMs` (type: `integer`):

Pause between requests so the source is not hit too quickly.

## Actor input object example

```json
{
  "districts": [
    "서울 강남구",
    "서울 종로구"
  ],
  "buildingTypes": [],
  "includeCancelled": false,
  "excludeShareDeals": false,
  "requestDelayMs": 400
}
```

# Actor output Schema

## `transactions` (type: `string`):

Every reported commercial sale with price, area, zoning and use class.

# 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 = {
    "districts": [
        "서울 강남구",
        "서울 종로구"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("loopchips/korea-commercial-trades").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 = { "districts": [
        "서울 강남구",
        "서울 종로구",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("loopchips/korea-commercial-trades").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 '{
  "districts": [
    "서울 강남구",
    "서울 종로구"
  ]
}' |
apify call loopchips/korea-commercial-trades --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,loopchips/korea-commercial-trades"
        }
    }
}

```

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/tHoVpl0e4t0oA08xL/builds/zq14ZxYuK08MbTiFd/openapi.json