# Japan Care Facilities (MHLW Open Data, CC BY) (`jpopendata/japan-care-facilities`) Actor

All Japanese long-term care providers (nursing homes, home care, day care, group homes and 30+ more registers) from the official MHLW 介護サービス情報公表システム open data (CC BY). English field schema, prefecture and service-type filters, corporate numbers, geocoordinates, source attribution embedded in ever…

- **URL**: https://apify.com/jpopendata/japan-care-facilities.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 $1.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 Care Facilities (MHLW Open Data, CC BY)

**Japan's long-term care providers — nursing homes, home care, day care, group homes and 31 more service types — as English-schema JSON with contact details.**

This Actor delivers the official open data of the 介護サービス情報公表システム (Long-Term Care Information Publication System), published by the Ministry of Health, Labour and Welfare under **Creative Commons CC BY**: provider name, service type, address, coordinates, published phone/fax, corporate number and corporate name, capacity, available days, and a direct link to each facility's page on the official kaigokensaku search site.

> **Unofficial tool.** Not affiliated with or endorsed by MHLW or the Government of Japan.
> **Attribution:** 本データは介護サービス情報公表システムから抽出したデータです。This CC BY attribution is embedded in the `license` string of **every output record**, so datasets you build downstream carry it automatically.

***

### Who is this for?

- **Elder-care market entry & B2B sales** — suppliers of care equipment, food services, staffing, and software building target lists of Japan's care providers, one of the world's largest and fastest-aging care markets. Published switchboard numbers and corporate identifiers make this directly usable as a lead list.
- **Investors & analysts** — mapping capacity and operator concentration by region and service type, with corporate numbers for entity matching against other registries.
- **Data & AI teams** — a clean provider master keyed by the official 10-character provider ID, with stable service-type codes.

### What you get

- **35 official service types**, selectable by 3-digit code, exact Japanese name, or `"all"` — from special nursing homes (介護老人福祉施設) to home care, day care, group homes, and care medical facilities.
- **Corporate linkage**: `corporateNumber` (the national 13-digit legal-entity number) and `corporateName` on each record — join care facilities to their operating companies.
- **Verified detail links**: `detailUrl` resolves to the facility's page on the official kaigokensaku.mhlw.go.jp site (URL pattern verified against the live site).
- **Honest handling**: not-geocoded `0` coordinates become `null`; capacity `0` ("not applicable/no limit" upstream usage) and blank are kept distinct.

### Sample output (dataset item)

```json
{
  "facilityId": "0170100000",
  "name": "特別養護老人ホーム ○○園",
  "nameKana": "トクベツヨウゴロウジンホーム マルマルエン",
  "serviceType": { "code": "510", "ja": "介護老人福祉施設", "en": "Special nursing home for the elderly" },
  "prefecture": { "code": "01", "nameJa": "北海道", "nameEn": "Hokkaido" },
  "city": "札幌市東区",
  "address": "北海道札幌市東区○○条○丁目1-1",
  "latitude": 43.0894,
  "longitude": 141.3849,
  "phone": "011-000-0000",
  "corporateNumber": "1234567890123",
  "corporateName": "社会福祉法人○○会",
  "capacity": 80,
  "availableDays": ["月", "火", "水", "木", "金", "土", "日"],
  "detailUrl": "https://www.kaigokensaku.mhlw.go.jp/01/index.php?action_kouhyou_detail_022_kani=true&JigyosyoCd=0170100000-00&ServiceCd=510",
  "snapshotMonth": "2026-06",
  "source": "介護サービス情報公表システム（厚生労働省）",
  "sourceUrl": "https://www.mhlw.go.jp/stf/kaigo-kouhyou_opendata.html",
  "license": "CC BY — 本データは介護サービス情報公表システムから抽出したデータです",
  "retrievedAt": "2026-08-25T09:12:44Z"
}
```

### Input example

```json
{
  "serviceTypes": ["510", "550"],
  "prefecture": "福井県",
  "maxItems": 500
}
```

`serviceTypes` accepts 3-digit codes, exact Japanese service names, or `"all"` (35 types). `prefecture` accepts JIS codes, Japanese, or English names.

### Pricing

Pay per result — see the pricing tab. A prefecture-level pull of one service type is typically tens to hundreds of records.

### FAQ

**Where does the data come from, and can I reuse it?**
From the official open-data CSVs of the 介護サービス情報公表システム, published by MHLW under **Creative Commons CC BY** with the condition that reuse states the data was extracted from the publication system. This Actor embeds that exact statement in every record's `license` field — your downstream datasets stay compliant by default. (Check the CC BY terms yourself before large-scale republication; this is not legal advice.)

**Is this an official government service?**
No. This is an **unofficial** tool, built and maintained independently, using officially published open data.

**How fresh is the data?**
MHLW publishes snapshots **twice a year** (end of June / end of December). The Actor always picks the newest one and stamps `snapshotMonth` on every record. That's the source's real cadence — we won't pretend it's live data.

**Are the phone numbers personal data?**
No — `phone`/`fax` are each facility's **published switchboard**, corporate contact information from the official open data. The published CSVs contain no person-name columns (verified on the current snapshot), and the Actor enforces this structurally: whitelist extraction, pattern-based exclusion of any future name/director/representative columns, and an automated legal test asserting that phone-shaped strings appear *only* in the `phone`/`fax` fields and no e-mail or personal-name-shaped strings appear anywhere.

**How big can a run get?**
`"all"` service types nationwide means 36 polite upstream requests (~100 MB transferred) and a few minutes of runtime — the Actor keeps ≥1.2 s between requests, backs off on 429/5xx, and never evades rate limits. Prefecture- or type-scoped runs are much lighter.

### Search terms this Actor answers

Japan nursing home database · Japan long-term care facilities · elderly care providers Japan · kaigo data English · Japan care homes list · Japan aging market data · 介護事業所 open data · Japan senior care leads

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

- **Japan Government Tenders & Awards** — tender notices and award results from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **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 Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.

***

*Data source: 介護サービス情報公表システム（厚生労働省）— https://www.mhlw.go.jp/stf/kaigo-kouhyou\_opendata.html . License: CC BY with the extraction statement above, embedded in every record.*

# Actor input Schema

## `serviceTypes` (type: `array`):

Which service registers to output, as 3-digit codes (one open-data CSV each; 1 polite download per code). Pass \["all"] for every register (~250k facilities, 35 downloads). Codes: 110 訪問介護, 120 訪問入浴介護, 130 訪問看護, 140 訪問リハ, 150 通所介護, 155 療養通所介護, 160 通所リハ, 170 福祉用具貸与, 210 短期入所生活介護, 220/230/551 短期入所療養介護, 320 認知症GH, 331/332/334/335/336/337 特定施設, 361/362/364 地域密着型特定施設, 410 特定福祉用具販売, 430 居宅介護支援, 510 介護老人福祉施設, 520 介護老人保健施設, 530 介護療養型医療施設, 540 地域密着型介護老人福祉施設, 550 介護医療院, 710 夜間対応型訪問介護, 720 認知症対応型通所介護, 730 小規模多機能, 760 定期巡回, 770 看護小規模多機能, 780 地域密着型通所介護.

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

Optional filter. Accepts a JIS code (`13`), a Japanese name (`東京都`) or an English name (`Tokyo`). Leave empty for nationwide.

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

Maximum number of records to output across all selected service types (in the order given).

## `openDataPageUrl` (type: `string`):

Advanced. Normally the actor reads the official MHLW open-data page (https://www.mhlw.go.jp/stf/kaigo-kouhyou\_opendata.html) and picks the newest snapshot section automatically. Pass an https URL here only for testing against a mirrored copy of that page.

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

Hard safety cap on upstream HTTP requests (politeness). A run needs 1 (page) + 1 per requested service type; the run stops gracefully when the cap is hit.

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

Apify proxy settings. Default is NO proxy (direct connection). The actor backs off exponentially on 429/5xx and fails visibly on a persistent block — it never attempts rate-limit evasion.

## Actor input object example

```json
{
  "serviceTypes": [
    "510"
  ],
  "prefecture": "Tokyo",
  "maxItems": 100,
  "maxApiRequests": 40,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-care-facilities").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("jpopendata/japan-care-facilities").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 jpopendata/japan-care-facilities --silent --output-dataset

```

## MCP server setup

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

```

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/PcKwL8ynrbRq0Dvg6/builds/hcBVt5e6AMjWO4KyS/openapi.json