Japan Restaurants Scraper (HotPepper Gourmet)

Restaurant data from HotPepper Gourmet (ホットペッパーグルメ) — Japan's biggest restaurant reservation site — by prefecture and cuisine genre, in a clean English schema: budgets, addresses, business phone numbers, opening hours, seat counts, private rooms and other facility facts.

This Actor scrapes public hotpepper.jp listing pages (and optionally each restaurant's detail page) and returns structured JSON: restaurant name, genre, sub-area, lunch/dinner budget ranges as parsed yen values, access line, street address, published business phone, opening hours, closed days, nearest station, coordinates — plus the facility facts HotPepper is uniquely strong at: total seats, maximum banquet capacity, private rooms, tatami/horigotatsu seating, counter seats, charter availability, Wi-Fi, parking, smoking policy, all-you-can-drink/eat and credit-card acceptance.

Unofficial tool. Not affiliated with or endorsed by Recruit Co., Ltd. or HotPepper Gourmet. This Actor reads public web pages only — it does not use the リクルートWEBサービス (HotPepper Gourmet) API. It collects publicly available factual business data only — it never collects review text (口コミ, copyrighted works), reviewer identities, staff data, coupon or advertising copy, and it never bypasses logins or CAPTCHAs. You are responsible for using the data in compliance with the source site's terms and the laws that apply to you (including GDPR/APPI where relevant); the published business phone numbers are included as business contact information, not personal data — verify your own legal basis before using them for outreach.

---

Quick start — verified input

Copy-paste this into the Actor's input (JSON tab) or pass it via API — it was run successfully on 2026-09-02 (10 izakaya around Shinjuku, Tokyo, listing data only, ~20 seconds):

{
  "prefecture": "Tokyo",
  "genre": "G001",
  "area": "新宿",
  "maxItems": 10
}

Common input mistakes

Wrong	Right	Why
"prefecture": "Osaka-shi" / "Yokohama" / "Shinjuku"	"prefecture": "Osaka" / "Kanagawa" / "Tokyo"	prefecture must be one of the 47 prefectures (English name, dropdown). Cities go in area (Japanese), or nowhere.
"prefecture": "東京都" or "13" (via API)	"prefecture": "Tokyo"	The platform checks the 47 English names before the run starts; other spellings are rejected with the valid list.
"genre": "izakaya" (via the UI dropdown / API)	"genre": "G001"	The schema takes the 17 G-codes; via API the English alias and Japanese label are also accepted by the actor.
"genre": "sushi"	leave genre empty, or "G004" (和食)	HotPepper has 17 top-level genres only — no sushi/ramen-level split except ラーメン (G013).
"area": "Shibuya"	"area": "渋谷"	The area filter is matched against Japanese station/address text; romaji matches nothing (the run warns).
"maxItems": "100"	"maxItems": 100	Numbers are numbers in JSON — the platform rejects a numeric string before the run starts.

Every invalid value stops the run immediately (before any upstream request) with a message that names the field and lists the valid values. Fields with a fixed list of values are validated by the Apify platform before the run even starts.

Empty results?

A run that finishes with items: 0 and complete: true is not an error. Typical causes: an area written in romaji (use the Japanese place name), an area that lies outside prefecture (e.g. "横浜" with "prefecture": "Tokyo"), or a genre with few listings in a rural prefecture. With area set, the actor scans listing pages and skips non-matching restaurants, so raise maxApiRequests for rare combinations.

---

Who is this for?

• B2B suppliers and services — lead lists of restaurants by prefecture and genre with published business phones, seat counts and banquet capacity (the classic signal for wholesale, POS, staffing and reservation-tech leads).
• Market research and location intelligence — density, budget positioning and facility mix of restaurants by area and cuisine.
• Travel and food-tech products — English-schema Japanese restaurant data including private-room and smoking-policy facts that international diners actually ask about.

Sample output (dataset item)

{
  "restaurantName": "居酒屋 よりみち 八王子店",
  "genre": ["居酒屋"],
  "budgetDinner": { "raw": "2001～3000円", "minJpy": 2001, "maxJpy": 3000 },
  "budgetLunch": null,
  "address": "東京都八王子市三崎町2-13",
  "prefecture": "東京都",
  "prefectureEn": "Tokyo",
  "prefectureCode": "13",
  "area": "八王子",
  "nearestStation": "八王子",
  "access": "八王子駅より徒歩１分。駅を出て左手に進み、サンドラックの角を左折した先にございます。",
  "phone": "042-686-1808",
  "businessHours": "月～木、日、祝日: 16:00～翌1:00 （料理L.O. 翌0:00 ドリンクL.O. 翌0:00） 金、土、祝前日: 16:00～翌4:30 ...",
  "closedDays": "無休",
  "seats": 150,
  "maxBanquetCapacity": 150,
  "privateRoom": true,
  "tatami": true,
  "horigotatsu": true,
  "counterSeats": false,
  "charterAvailable": true,
  "wifi": false,
  "parking": true,
  "smoking": "全席喫煙可",
  "allYouCanDrink": true,
  "allYouCanEat": false,
  "creditCard": "利用不可",
  "latitude": 35.6569119,
  "longitude": 139.337419,
  "url": "https://www.hotpepper.jp/strJ001284014/",
  "hotpepperId": "J001284014",
  "detailFetched": true,
  "source": "ホットペッパーグルメ (HotPepper Gourmet, hotpepper.jp)",
  "sourceUrl": "https://www.hotpepper.jp/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T14:24:46.000Z"
}

In cheap list-only mode (detailFetch: false, the default) each listing page request yields 20 records with name, genre, sub-area, budgets, access line, phone (when the cassette lists one) and coordinates; the detail-only fields are null.

Input reference

{
  "prefecture": "Tokyo",
  "genre": "G001",
  "area": "新宿",
  "maxItems": 40,
  "detailFetch": true,
  "maxApiRequests": 60
}

• prefecture (required): English name of one of the 47 prefectures exactly as in the dropdown ("Tokyo", "Osaka" …). The Apify platform validates this list before the run starts, so "東京都", "13" or "tokyo-to" are rejected immediately with the list of valid values. Cities are not prefectures — "Yokohama" is rejected; use "Kanagawa".
• genre (optional): one of the 17 HotPepper genre codes (G001 居酒屋 … G017 韓国料理, dropdown). Leave empty to walk all 17 genres in site order. Via API the Japanese label or an English alias (izakaya, ramen, yakiniku, italian, chinese, bar, cafe, korean …) is accepted too; anything else is refused with the full list.
• area (optional): a Japanese place-name substring ("新宿", "渋谷") matched client-side against sub-area, access line, station and address. Romaji matches nothing (the run warns); prefecture names are refused.
• maxItems (default 10, max 1000) / maxApiRequests (default 15, max 60) / detailFetch (default false) / proxyConfiguration (default none).

Pricing

Pay per result — see the pricing tab. A listing-only run is cheap (20 records per upstream request); detailFetch: true costs one extra upstream request per restaurant and fills the business-info and facility fields.

FAQ

Where does the data come from? Live from public hotpepper.jp listing and store detail pages at run time. Every record embeds the source, source URL, a license note and the retrieval timestamp.

Is this an official HotPepper/Recruit service? Does it use the HotPepper API? No and no. Unofficial, independently built and maintained, not affiliated with or endorsed by Recruit Co., Ltd. It deliberately does not use the リクルートWEBサービス API — it reads the public web pages.

Does it collect reviews, coupons or ad copy? No, by design. Review text is a copyrighted work and reviewer identities are personal data — review pages (/report/) are never requested, and the URL guard refuses them outright. Advertising cassettes (【PR】) are skipped, and coupon copy, catch copy and SEO keyword lines are never parsed. Automated tests assert with real-page specimens that none of this can ever appear in the output.

Where do the phone numbers come from? From the page's own structured business data (JSON-LD telephone and the listing's data attributes). The /tel/ phone-reveal endpoint is never requested.

Why did my run stop before maxItems? The Actor enforces a hard per-run request budget (maxApiRequests) with strictly serial requests ≥1.2 s apart — polite by construction. The run summary (RUN_SUMMARY key-value record) reports complete: false with the reason whenever a budget truncated the result set. Raise maxApiRequests or narrow the query.

What if hotpepper.jp blocks the datacenter IP? The Actor performs no block evasion (no header spoofing, no CAPTCHA solving, no rotation tricks). If the runtime IP is refused mid-crawl the run keeps the records it already collected, ends successfully with complete: false and a stopReason in RUN_SUMMARY, and you are billed only for the records actually delivered; a run refused before its first record fails visibly with the HTTP status. Setting proxyConfiguration (e.g. Apify automatic proxy, or residential with apifyProxyCountry: "JP") usually resolves it — one sticky egress IP is used for the whole run.

Is the whole of Japan covered? Yes — all 47 prefectures and all 17 HotPepper cuisine genres. What one run returns is your query's result set subject to maxItems and the request budget, both reported honestly in the run summary.

Search terms this Actor answers

hotpepper scraper · hotpepper gourmet API · Japan restaurant data · Japanese restaurant database · Tokyo izakaya list · Japan restaurant leads · restaurant phone numbers Japan · private room restaurants Tokyo data · Japan food and beverage market research · ホットペッパーグルメ データ · restaurant seats capacity dataset Japan · Japan restaurant reservation data

More Japan data Actors by the same developer

• Japan Restaurants Scraper (Tabelog) — the same aligned schema over tabelog.com with the famous Tabelog rating: use it when you need the quality signal; use this Actor for facility facts and reservation-side coverage.
• Japan Restaurants Scraper (Gurunavi) — the same aligned schema over r.gnavi.co.jp, where shops publish their own business phone numbers: the strongest source for restaurant B2B lead lists.
• Japan Beauty Salons Scraper (HotPepper Beauty) — salons with seats, staff counts and price anchors from beauty.hotpepper.jp.
• 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 Construction & Real-Estate Licenses — licensed contractors and brokers from MLIT's official register.

---

Data source: hotpepper.jp public pages. Unofficial; not affiliated with Recruit Co., Ltd. Factual business data only — no review content, no user data, no coupon/ad copy. Users are responsible for their own compliance with the source site's terms and applicable law.