MOLIT Apartment Actual Transaction Prices
MOLIT actual-transaction price service for apartments, detached houses, and row houses by administrative district. Official MOLIT RTMS API.
What agents get
- Apartment name, exclusive area, transaction price, floor, construction year, road-name address, legal-district code, and transaction year-month
Real-estate price analysis, regional housing-price trends, market monitoring, and investment decision support
Use cases
- Look up apartment transactions by region
- Compare prices across apartments
- Analyze monthly volume and price trends
- Search by legal-district code
Registered APIs (1)
Apartment Transaction Price Lookup getRTMSDataSvcAptTrade
Look up apartment transactions by legal-district code and transaction year-month
LAWD_CDRequired — First 5 digits of the legal-district code (sigungu) e.g.11110DEAL_YMDRequired — Transaction year-month YYYYMM e.g.202609numOfRowsOptional e.g.10pageNoOptional e.g.1
Returns: Apartment name, Exclusive area (sqm), Transaction price (in 10,000 KRW), Floor, Construction year, Road name, Legal-district sigungu code, Legal-district eup/myeon/dong code, Transaction year-month
Rate limit: 10,000 calls/day (Per data.go.kr development-account quota)
Auth · pricing · terms
| Auth | ServiceKey — data.go.kr service key. Stored only on the proxy server. |
|---|---|
| Pricing | Free. Auto-approved |
| License | Public data: attribution required (Type 1) + author credit (CC BY) |
| Redistribution | Allowed (attribution required) |
| Terms checked | 2026-10-10 |
| Apply | Log in to the data.go.kr portal -> Apply for the MOLIT actual-transaction price service -> Service key issued (auto-approved) Portal |
| Status | Coming soon (opens after key registration) |
| Last checked | 2026-10-10 |
How agents call
Call through our proxy. Start with the keyless quick API shown above (no token needed). For the keyed proxy, send X-Agent-Token to POST /agencatalog/api/call with ('service', 'endpoint', 'params'). The full service list is at /agencatalog/api/services.json.
Example: POST /agencatalog/api/call {service:'rtms-apt-trade', endpoint:'getRTMSDataSvcAptTrade', params:{LAWD_CD:'11110', DEAL_YMD:'202609'}}
Machine-readable JSON schema
{
"service": "rtms-apt-trade",
"name": "MOLIT Apartment Actual Transaction Prices",
"provider": "MOLIT",
"apis": [
{
"id": "getRTMSDataSvcAptTrade",
"name": "Apartment Transaction Price Lookup",
"params": [
{
"name": "LAWD_CD",
"required": true,
"example": "11110",
"desc": "First 5 digits of the legal-district code (sigungu)"
},
{
"name": "DEAL_YMD",
"required": true,
"example": "202609",
"desc": "Transaction year-month YYYYMM"
},
{
"name": "numOfRows",
"required": false,
"example": "10"
},
{
"name": "pageNo",
"required": false,
"example": "1"
}
]
}
],
"proxy_call": "POST /agencatalog/api/call",
"attribution": "Source: MOLIT Actual Transaction Price Service (Public Data Portal data.go.kr)"
}
Notes
- API keys live only on the server. Clients asking for keys directly cannot use this route.
- Each provider has a daily quota. Over-quota calls return 429 and are blocked.
- Provider outages or over-quota errors are passed through. Check the error field before retrying.
- Attribution: Source: MOLIT Actual Transaction Price Service (Public Data Portal data.go.kr)
Last checked: 2026-10-10
AI Knowledge Hub