# Japan Beauty Salons (beauty.hotpepper.jp) (`jpopendata/japan-beauty-salons`) Actor

Japanese beauty salon business listings from beauty.hotpepper.jp — hair, nail, eyelash, relaxation and esthetic salons with address, hours, seat/staff counts and entry prices by prefecture, English schema. Unofficial; not affiliated with Recruit Co., Ltd.

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

## Pricing

from $4.00 / 1,000 per 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 Beauty Salons (beauty.hotpepper.jp)

**Japanese beauty-salon business listings — hair, nail, eyelash, relaxation and esthetic salons with address, hours, seat/staff counts and entry prices — from beauty.hotpepper.jp, Japan's largest salon reservation platform, in a clean English schema.**

This Actor searches beauty.hotpepper.jp's public salon listings by prefecture and vertical and returns each salon as English-schema JSON: salon name (plus kana reading), service type, station/access line, seat count and entry price. With `detailFetch` it adds the street address and city, business phone (as published in the page's structured data), business hours, closed days, staff count and feature tags (private rooms, card payment, late-night hours, …) from each salon's detail page. An optional `area` keyword narrows results client-side.

Japan has over 250,000 beauty salons — a huge, fragmented B2B market — but the leading directory is Japanese-only and invisible to most international tooling. This Actor is the bridge for anyone selling **to** salons or analyzing the market.

> **Unofficial tool.** Not affiliated with or endorsed by Recruit Co., Ltd. or HOT PEPPER Beauty. It collects **publicly available data only** (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion), and extracts **factual business data only** — salon facts and business identity; **no stylist or staff personal names or photos ever** (staff figures are counts only), no review content, no salon marketing copy, no coupon data (relevant e.g. under GDPR: no personal data is collected or processed). It reads the public web pages only — the Recruit WEB Service API is deliberately not used. Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

***

### Who is this for?

- **Beauty equipment & cosmetics distributors** — build prefecture-by-prefecture prospect lists of hair/nail/eyelash/esthetic salons with seat counts (a direct proxy for salon size and equipment spend).
- **Salon SaaS & booking-tool sales** — lead lists with staff counts, business hours and feature tags to segment by salon size and digital readiness.
- **Market analysis & site selection** — salon density, price levels and service mix by prefecture, city and station area.
- **Data teams** — a stable English schema over a Japanese-only source.

### Sample output (dataset item)

```json
{
  "salonName": "Grege【グレージュ】",
  "salonNameKana": "グレージュ",
  "serviceType": "hair",
  "address": "東京都渋谷区東３-25-8 ACN EBISU 2F",
  "prefecture": "東京都",
  "prefectureEn": "Tokyo",
  "prefectureCode": "13",
  "city": "渋谷区",
  "nearestStation": "恵比寿駅徒歩2分",
  "phone": "03-6427-5357",
  "businessHours": "平日/11：00～21：00（最終受付/20：00）、土曜/10：00～20：00（最終受付/19：00）、日祝/10：00～19：00（最終受付/18：00）",
  "closedDays": "毎週火曜日 年末年始",
  "seatCount": 5,
  "staffCount": 4,
  "priceRange": "￥6,600～",
  "features": ["夜19時以降も受付OK", "ロング料金なし", "最寄り駅から徒歩3分以内にある", "店頭でのカード支払いOK", "禁煙", "ドリンクサービスあり", "個室あり", "半個室あり"],
  "url": "https://beauty.hotpepper.jp/slnH000272162/",
  "detailFetched": true,
  "source": "ホットペッパービューティー (beauty.hotpepper.jp)",
  "sourceUrl": "https://beauty.hotpepper.jp/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T13:10:00Z"
}
```

### Input example

```json
{
  "prefecture": "Tokyo",
  "serviceType": "hair",
  "area": "渋谷",
  "detailFetch": true,
  "maxItems": 50
}
```

`prefecture` is required (JIS code, Japanese or English name). `serviceType` is one of `hair` (default), `nail`, `eyelash`, `relaxation`, `esthe`. `area` filters client-side on the station/access line, address and city (address/city need `detailFetch`).

### Pricing

Pay per result — see the pricing tab. A prefecture × vertical query is typically thousands of salons upstream (Tokyo hair alone: ~9,000); `maxItems` caps what you take.

### FAQ

**Where does the data come from?**
Live from beauty.hotpepper.jp's public, login-free prefecture list pages and salon detail pages at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

**Is this an official HOT PEPPER Beauty / Recruit service?**
No. **Unofficial**, independently built and maintained, and **not affiliated with or endorsed by Recruit Co., Ltd.** It reads only publicly available pages. The Recruit WEB Service API is deliberately not used.

**Are stylist names, reviews or coupons included?**
No, deliberately. Stylist/staff **personal names, kana readings and photos are never extracted** — beauty salons are small businesses where personal data bleeds into salon content, so parsing is strict whitelist-only and staff figures are **counts only** (e.g. `staffCount: 4`). Review bodies, scores, counts and reviewer names are never extracted (user-generated copyrighted content), and neither are salon catch copy, coupon names/prices, or the SEO keyword tails salons append to their listings. The output is strictly factual salon business data.

**Why do some fields come back null?**
Address, city, kana name, phone, hours, closed days and features live on the salon detail page — set `detailFetch: true` (one extra request per salon). List-only runs still return name, station line, seat count and (for hair) the entry cut price. The phone is included only when the salon publishes it in the page's structured data; the site's on-page "reveal number" endpoints are never touched.

**Who is responsible for how the data is used?**
You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms, telemarketing rules) is your responsibility as the user.

**What about server load?**
Strictly serial requests, ≥1.2 s apart, 20 salons per list page, one extra request per salon detail (opt-in), hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If beauty.hotpepper.jp changes its page format, the Actor stops with a clear error instead of silently mis-parsing; if it blocks persistently, the run fails visibly.

### Search terms this Actor answers

japan beauty salon database · hair salon leads japan · japan salon market data · hot pepper beauty scraper · hotpepper beauty scraper · japan nail salon list · japan eyelash salon data · japan esthetic salon leads · beauty salon prospect list japan · 美容室 リスト · サロン データ · japan salon SaaS leads · beauty industry japan dataset · salon count by prefecture japan

### More Japan data Actors by the same developer

- **Japan Hotels & Ryokan Prices** — hotel/ryokan prices and facility facts from jalan.net.
- **Japan Used Cars (carsensor.net)** — used-vehicle listings with price, mileage and repair history.
- **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 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 Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's official register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.

***

*Unofficial tool; not affiliated with Recruit Co., Ltd. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data is collected — business facts only, staff figures as counts.*

# Actor input Schema

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

REQUIRED. Prefecture of the salons: JIS code ("13"), Japanese ("東京都") or English ("Tokyo"). beauty.hotpepper.jp list pages are prefecture-scoped.

## `serviceType` (type: `string`):

Salon vertical: hair (default), nail, eyelash, relaxation or esthe. Each maps to the corresponding beauty.hotpepper.jp search vertical.

## `area` (type: `string`):

Optional case-insensitive substring filter on the salon's access/station line, address and city (e.g. "渋谷", "恵比寿" — Japanese matches best), applied client-side after parsing. Address/city only match when detailFetch is on.

## `detailFetch` (type: `boolean`):

When true, each salon costs one extra request but adds street address, city, kana name, business phone (as published in the page's structured data), business hours, closed days, feature tags and more precise seat/staff counts. When false (default) the actor emits list data only (name, station line, seat count, entry price) — cheaper.

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

Stop after this many dataset records.

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

Hard budget of HTTP requests to beauty.hotpepper.jp for this run (list pages of 20 salons + 1 per salon detail when detailFetch is on). 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 — one client identity per run.

## Actor input object example

```json
{
  "prefecture": "Tokyo",
  "serviceType": "hair",
  "area": "渋谷",
  "detailFetch": false,
  "maxItems": 10,
  "maxApiRequests": 30
}
```

# Actor output Schema

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

Structured beauty-salon business 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",
    "serviceType": "hair",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-beauty-salons").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",
    "serviceType": "hair",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-beauty-salons").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",
  "serviceType": "hair",
  "maxItems": 10
}' |
apify call jpopendata/japan-beauty-salons --silent --output-dataset

```

## MCP server setup

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

```

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/1K92FRmiPsAjr18gW/builds/j4uRgJT5zvwOr2mtO/openapi.json