# Japan Construction & Real-Estate License Roster (MLIT) (`jpopendata/japan-construction-licenses`) Actor

Licensed Japanese construction contractors and real-estate brokers from the MLIT company-information search system (etsuran2.mlit.go.jp): license number, licensing authority, held construction industries, validity period and municipality-level address, filtered by prefecture, industry or name. En…

- **URL**: https://apify.com/jpopendata/japan-construction-licenses.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 records

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?

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

## Japan Construction & Real-Estate Licenses (MLIT)

**Licensed Japanese construction contractors and real-estate brokers, from MLIT's official register — filterable by industry and region, with license numbers and validity dates.**

This Actor searches the Ministry of Land, Infrastructure, Transport and Tourism's official company-information system (建設業者・宅建業者等企業情報検索システム, etsuran2.mlit.go.jp) — the register behind Japan's roughly 470,000 construction licenses — and returns corporate license holders as English-schema JSON: company name with katakana reading, license number and issuing authority, the held construction industries (29 statutory categories, English names, general/specific class), license validity period as ISO dates, capital, and municipality-level location.

> **Unofficial tool.** Not affiliated with or endorsed by MLIT or the Government of Japan. Records are edited/processed data from the register (出典：国土交通省 建設業者・宅建業者等企業情報検索システムを編集・加工して作成), published under 公共データ利用規約（第1.0版）(PDL 1.0) — commercial reuse permitted with attribution and a processed-data notice, both embedded in every record.

***

### Who is this for?

- **B2B sales to the construction sector** — construction machinery, building materials, insurance, and SaaS vendors building lead lists of licensed contractors by industry (e.g., all governor-licensed roofing contractors in Osaka) with license class and capital as qualifiers.
- **Proptech and real-estate teams** — enumerate licensed brokers (宅地建物取引業者) by region, with license renewal counts as a longevity signal.
- **Counterparty verification** — confirm a contractor's license number, held industries, class, and validity period against the official register before contracting.

### Sample output (dataset item)

```json
{
  "companyName": "（株）○○建設",
  "companyNameKana": "マルマルケンセツ",
  "businessType": "construction",
  "licenseNo": "第011808号",
  "licenseAuthority": "福井県",
  "licenseType": "governor",
  "industries": [
    { "code": 1, "abbrJa": "土", "nameJa": "土木工事業", "nameEn": "Civil engineering", "licenseClass": "general" },
    { "code": 2, "abbrJa": "建", "nameJa": "建築工事業", "nameEn": "Building construction", "licenseClass": "general" }
  ],
  "prefecture": "福井県",
  "prefectureCode": "18",
  "prefectureEn": "Fukui",
  "address": "福井県福井市",
  "validFrom": "2024-01-30",
  "validTo": "2029-01-29",
  "capitalThousandJpy": 5000,
  "entityVerification": "corporate",
  "detailFetched": true,
  "source": "国土交通省 建設業者・宅建業者等企業情報検索システム",
  "sourceUrl": "https://etsuran2.mlit.go.jp/TAKKEN/",
  "license": "公共データ利用規約（第1.0版）PDL1.0 — 編集・加工して作成",
  "retrievedAt": "2026-08-25T09:12:44Z"
}
```

### Input example

```json
{
  "businessType": "construction",
  "prefecture": "Osaka",
  "industryCode": "8",
  "industryType": "general",
  "licenseType": "governor",
  "maxItems": 200
}
```

At least one search criterion is required — unfiltered national dumps are not supported, by design. Filters: prefecture, one of the 29 statutory industries (+ general/specific class), partial company name (kanji or katakana), minister vs governor license.

### Pricing

Pay per result — see the pricing tab. A prefecture × industry roster is typically tens to a few hundred records.

### FAQ

**Where does the data come from?**
Live from MLIT's official search system, which the ministry updates about **twice a month** for the construction and real-estate registers. Every record embeds the source, the register URL, the PDL 1.0 license designation, and the retrieval timestamp.

**Is this an official government service?**
No. **Unofficial**, independently built and maintained, using MLIT's publicly available register under PDL 1.0 with the required attribution.

**Are sole proprietors included?**
No — corporate entities only, and honestly enforced: the register itself records a 法人・個人区分 (corporate/individual) flag, and the Actor excludes individuals using that authoritative flag (in cheap list-only mode, a conservative corporate-name test is used instead, and `entityVerification` tells you which check each record passed). Representative names and phone numbers are **never extracted** — the parser locates those columns specifically so it can refuse to read them — and addresses are truncated to municipality level. A run summary reports how many records were excluded, so the filtering is visible.

**Why is the address only city-level?**
Deliberate privacy posture (small operators' registered addresses can be homes) — and for lead-list and verification use cases, prefecture + municipality is what you actually need. If address parsing is ambiguous, the Actor falls back to prefecture only; it never errs toward leaking a street address.

**Is this every licensed contractor in Japan?**
The register is the official national one (construction licenses on the order of 470,000). What one run returns is your search's result set, subject to your filters, `maxItems`, and the polite request budget — the run summary flags `complete: false` whenever a budget truncated the roster, so you always know whether you got everything you asked for.

**What about server load?**
Strictly serial requests, ≥1.2 s apart, 50 rows per search page, one extra request per company detail, hard per-run budget, exponential backoff, no block evasion. If the site's format changes, the Actor stops with a clear error instead of silently mis-parsing.

### Search terms this Actor answers

Japan construction companies database · licensed contractors Japan · Japan general contractor list · 建設業許可 data English · Japan real estate broker license lookup · takken license search · Japan construction industry leads · MLIT contractor register

### More Japan public-data Actors by the same developer

- **Japan Government Tenders & Awards** — tender notices and award results (who wins public-works contracts) from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **Japan Care Facilities** — long-term care providers across 35 service types (MHLW open data, CC BY).
- **Japan Government Subsidies & Grants** — open subsidy calls from the official jGrants API.
- **Japan Renewable Energy FIT/FIP Facilities** — METI-certified renewable installations, privacy-safe schema.
- **Japan Financial Licenses & Registrations** — FSA-licensed banks, securities firms, crypto exchanges and more.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.

***

*Data source: 国土交通省 建設業者・宅建業者等企業情報検索システム — https://etsuran2.mlit.go.jp/TAKKEN/ . PDL 1.0; attribution and processing notice embedded in every record.*

# Actor input Schema

## `businessType` (type: `string`):

Which license register to search: `construction` (建設業者 — construction contractors licensed under the Construction Business Act) or `realestate` (宅地建物取引業者 — licensed real-estate brokers).

## `prefecture` (type: `string`):

Prefecture of the (head) office: JIS code ("18"), Japanese ("福井県") or English ("Fukui"). STRONGLY recommended — at least one search criterion (prefecture / companyName / industryCode / licenseType) is REQUIRED; a full national dump is not supported by design (source terms condition).

## `industryCode` (type: `string`):

Construction only. One of the 29 statutory license industries: numeric code 1-29, abbreviation ("電") or Japanese name ("電気工事業"). 1=土木 2=建築 3=大工 4=左官 5=とび・土工 6=石 7=屋根 8=電気 9=管 10=タイル 11=鋼構造物 12=鉄筋 13=舗装 14=しゅんせつ 15=板金 16=ガラス 17=塗装 18=防水 19=内装仕上 20=機械器具 21=熱絶縁 22=電気通信 23=造園 24=さく井 25=建具 26=水道施設 27=消防施設 28=清掃施設 29=解体.

## `industryType` (type: `string`):

Required by the upstream form whenever industryCode is set: `general` (一般建設業) or `specific` (特定建設業, large-scale subcontracting). Default general.

## `companyName` (type: `string`):

Partial match against the published trade name, without the corporate designator (upstream instruction: enter the name WITHOUT 株式会社/有限会社 etc., e.g. "井上建設" not "株式会社井上建設"). Katakana input searches the phonetic reading. Every row is additionally re-filtered client-side.

## `licenseType` (type: `string`):

`minister` = licensed by the Minister of Land, Infrastructure, Transport and Tourism (offices in 2+ prefectures), `governor` = licensed by a prefectural governor, `any` = both.

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

When true (default), each record costs one extra request but includes held industries, license validity period, capital and the authoritative corporate/individual flag (sole proprietors are excluded using it). When false the actor emits list rows only — cheaper, but only names carrying an explicit corporate designator are emitted (all others are excluded as unverifiable).

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

Stop after this many dataset records.

## `maxApiRequests` (type: `integer`):

Hard budget of HTTP requests to etsuran2.mlit.go.jp for this run (search pages of 50 rows + 1 per detail). Requests are strictly serial with >= 1.2 s spacing. When the budget runs out the run completes with complete=false in RUN\_SUMMARY.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. Default: no proxy. Never used for rotation/evasion — a single session identity is kept per run.

## Actor input object example

```json
{
  "businessType": "construction",
  "prefecture": "Fukui",
  "industryCode": "8",
  "industryType": "general",
  "companyName": "井上建設",
  "licenseType": "any",
  "includeDetails": true,
  "maxItems": 30,
  "maxApiRequests": 10
}
```

# Actor output Schema

## `records` (type: `string`):

Structured records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# 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 = {
    "prefecture": "tokyo",
    "companyName": "建設"
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-construction-licenses").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 = {
    "prefecture": "tokyo",
    "companyName": "建設",
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-construction-licenses").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 '{
  "prefecture": "tokyo",
  "companyName": "建設"
}' |
apify call jpopendata/japan-construction-licenses --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-construction-licenses"
        }
    }
}

```

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/5h4NXrsc0YspeGIM9/builds/pkZ9Lc0ld8wNuaJpK/openapi.json