Japan Restaurants Scraper (Tabelog)

Restaurant data from Tabelog (食べログ) — Japan's biggest restaurant guide — by prefecture, neighbourhood and cuisine, in a clean English schema: ratings, review counts, bookmark counts, budgets, addresses, phone numbers and opening hours.

This Actor scrapes tabelog.com listing pages (and optionally each restaurant's detail page) and returns structured JSON: restaurant name with kana reading, cuisine genres, the famous Tabelog rating (0-5 scale, where 3.5+ already means excellent), review and bookmark counts, lunch/dinner budget ranges as parsed yen values, nearest station, street address, published business phone, opening hours and coordinates.

Unofficial tool. Not affiliated with or endorsed by Kakaku.com Inc. or Tabelog. This Actor collects publicly available factual business data only — it never collects review text (copyrighted works), reviewer names or any other user data, 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 ramen shops in Shinjuku, Tokyo, listing data only, ~20 seconds; the default RESIDENTIAL JP proxy is applied automatically):

Proxy: tabelog.com blocks Apify datacenter IP ranges (HTTP 403), so this Actor uses Apify RESIDENTIAL proxies (country JP) by default — the Quick start above needs no proxy settings of your own. Proxy bandwidth is billed as Apify platform usage (a listing-only run of 10 records moves well under 1 MB).

{
  "prefecture": "Tokyo",
  "area": "shinjuku",
  "genre": "ramen",
  "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 and wards go in area, 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.
"area": "Osaka" or "area": "Tokyo"	leave area empty (or "area": "A1304")	area is a neighbourhood code/name, not a city/prefecture. Take the code from a tabelog listing URL.
"area": "Namba" (a non-Tokyo neighbourhood by name)	"area": "A2701/A270202" code copied from the site URL	Built-in English names exist for Tokyo only; every other neighbourhood works via its tabelog code.
"genre": "Ramen shops"	"genre": "ramen"	Use the slug from a tabelog listing URL; a non-existent slug stops the run with HTTP 404 and the list of known slugs.
"minRating": "3.5+"	"minRating": 3.5	A number between 0 and 5.
"proxyConfiguration": { "useApifyProxy": false }	keep the default (RESIDENTIAL, country JP)	tabelog.com answers HTTP 403 to datacenter IPs; the default residential proxy is required.

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 — the query matched nothing on tabelog. Typical causes: a high minRating combined with a small maxApiRequests (filtering is client-side, so raise the budget), an area code from a different prefecture than prefecture, or a very specific area + genre combination. Widen the query and re-run.

---

Who is this for?

• Market research and location intelligence — density, ratings and price points of restaurants by neighbourhood and cuisine (e.g. every ramen shop around Shinjuku station with rating and budget).
• Travel, food-tech and recommendation products — English-schema Japanese restaurant data with the Tabelog rating, the metric travellers actually trust.
• B2B suppliers and services — lead lists of restaurants by area and genre with published business contact details and budget positioning.

Sample output (dataset item)

{
  "restaurantName": "道産子 新宿西口店",
  "restaurantNameKana": "どさんこ",
  "genre": ["居酒屋", "海鮮"],
  "rating": 3.28,
  "reviewCount": 100,
  "bookmarkCount": 4626,
  "budgetDinner": { "raw": "￥3,000～￥3,999", "minJpy": 3000, "maxJpy": 3999 },
  "budgetLunch": null,
  "address": "東京都新宿区西新宿1-2-7 小杉ビル B1F",
  "prefecture": "東京都",
  "prefectureEn": "Tokyo",
  "prefectureCode": "13",
  "nearestStation": "新宿西口駅",
  "phone": "03-3342-2958",
  "businessHours": "月・火・水・木 16:00 - 23:45 L.O. 料理23:10 ドリンク23:30; 金・土 14:00 - 23:45 ...",
  "closedDays": null,
  "latitude": 35.6926975,
  "longitude": 139.699659,
  "url": "https://tabelog.com/tokyo/A1304/A130401/13051074/",
  "tabelogId": "13051074",
  "detailFetched": true,
  "source": "食べログ (Tabelog, tabelog.com)",
  "sourceUrl": "https://tabelog.com/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T09:12:44.000Z"
}

In cheap list-only mode (detailFetch: false, the default) each listing page request yields 20 records with name, genres, rating, review/bookmark counts, budgets, nearest station and URL; address/phone/hours fields are null.

Input reference

{
  "prefecture": "Tokyo",
  "area": "shinjuku",
  "genre": "ramen",
  "minRating": 3.5,
  "maxItems": 40,
  "detailFetch": true,
  "maxApiRequests": 60
}

• prefecture (required): English name of one of the 47 prefectures exactly as in the dropdown ("Tokyo", "Osaka", "Kyoto" …). 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".
• area (optional): a tabelog area code copied from any tabelog URL — A1304 (district block), A130401 (sub-area; parent derived automatically), C13104 (municipality) or a full path A1304/A130401/R5184 (station) — this works for every prefecture and neighbourhood in Japan. Convenience English names are built in for Tokyo (shinjuku, shibuya, ikebukuro, yoyogi, shinjuku-gyoen, okubo, shin-okubo; Shinjuku-ku and 新宿 also work). Unknown free text is refused with the list of valid values instead of guessing the wrong neighbourhood.
• genre (optional): a tabelog genre slug as seen in listing URLs (ramen, sushi, izakaya, cafe, yakiniku, italian, french, chinese, curry, sweets, yakitori, tonkatsu …) with aliases (bbq→yakiniku, coffee→cafe, noodles→ramen) and Japanese labels (ラーメン, 寿司 …). A slug that does not exist on tabelog stops the run with HTTP 404 and an explanation, never silent wrong data.
• minRating (optional, 0–5): client-side filter on the listing rating.
• maxItems (default 10, max 1000) / maxApiRequests (default 15, max 60) / detailFetch (default false) / proxyConfiguration (default RESIDENTIAL, country JP — required, see FAQ).

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 fields.

FAQ

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

Is this an official Tabelog/Kakaku.com service? No. Unofficial, independently built and maintained, not affiliated with or endorsed by Kakaku.com Inc. Tabelog is a trademark of its owner.

Does it collect reviews? No, by design. Review text is a copyrighted work and reviewer identities are personal data — the parser deletes the review array from the page's structured data before reading anything, and automated tests assert that no review text, reviewer name or review-shaped field can ever appear in the output. Only the numeric facts survive: the rating value, the review count, the bookmark count.

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.

Do I need a proxy? Yes — and it is on by default. tabelog.com blocks Apify datacenter IP ranges (HTTP 403; verified 2026-09-02 — the same URLs answer 200 from other networks), so the input's proxyConfiguration defaults to Apify RESIDENTIAL proxies with country JP. Keep that default; residential bandwidth is billed as Apify platform usage. The Actor performs no block evasion (no header spoofing, no CAPTCHA solving, no rotation tricks) — one serial session per run — and if the runtime IP is still refused it fails visibly with the HTTP status.

I need restaurant phone numbers for lead lists — is Tabelog the best source? Tabelog publishes a reservation line per shop, but Gurunavi is where restaurants publish their own business phone numbers. For phone-rich B2B lead data use the sibling Japan Restaurants Scraper (Gurunavi) — its schema is aligned with this one so the datasets join cleanly; use this Actor when you need the rating signal.

Is the whole of Japan covered? Yes — any prefecture, and any neighbourhood/station/municipality via its Tabelog area code. 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

tabelog scraper · Tabelog API · Japan restaurant data · Japanese restaurant database · Tokyo restaurants dataset · Japan restaurant ratings · ramen restaurants Tokyo data · Japan food guide scraping · restaurant leads Japan · 食べログ データ · Shinjuku Shibuya restaurant list · Japan restaurant market research

More Japan data Actors by the same developer

• 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 (plus seats, smoking policy, private rooms, parking, credit cards).
• 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 Construction & Real-Estate Licenses — licensed contractors and brokers from MLIT's official register.
• 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: tabelog.com public pages. Unofficial; not affiliated with Kakaku.com Inc. Factual business data only — no review content, no user data. Users are responsible for their own compliance with the source site's terms and applicable law.