Gurunavi Scraper — Japan restaurants, budgets & phone numbers (ぐるなび)

Pull structured restaurant data from Gurunavi / ぐるなび, one of Japan's largest restaurant directories. Search any cuisine in Japanese or English, filter by area, and export as JSON, CSV or Excel. No login, no browser, no proxy setup.

What you get

Default run (list only, fast):

{
  "shopNo": "dagvus5r0000",
  "url": "https://r.gnavi.co.jp/dagvus5r0000/",
  "name": "ラーメン 尹善栄の店",
  "genre": "塩ラーメン ラーメン",
  "lunchBudgetYen": null,
  "dinnerBudgetYen": 1000,
  "access": "ＪＲ西日暮里駅 徒歩2分",
  "photoUrls": ["https://rimage.gnst.jp/rest/img/dagvus5r0000/s_0n5o.jpg"],
  "photoCaption": "「透きとおった塩ラーメン」"
}

With Include detail page data every restaurant also carries the contact block:

{
  "phone": "03-5615-2487",
  "postalCode": "116-0013",
  "addressRegion": "東京都",
  "addressLocality": "荒川区",
  "streetAddress": "西日暮里5-11-1野田ビル1F",
  "cuisine": "ラーメン",
  "priceRange": "￥1,000",
  "openingHours": ["Mo,Tu,We,Th,Fr 11:00-15:00"],
  "amenities": ["カード可", "個室あり"],
  "description": "札幌すすきの名店いそつー姉妹店！…"
}

Who uses this

• Restaurant-tech & POS sales — a clean list of independent restaurants by area, with phone numbers, for outreach
• Food delivery & reservation platforms — find venues not yet on your platform, by genre and station
• Market research — lunch and dinner budgets are structured numbers, so you can chart price levels by ward or by cuisine
• Travel content & guides — genre, access from the nearest station, photos and opening hours in one row
• Location analysis — cross the address and station fields with your own foot-traffic data

How to use

1. Enter a keyword (ラーメン, sushi, 焼肉, izakaya) or leave it empty to list everything in the area
2. Set an area slug the way Gurunavi writes it: jp for all of Japan, or tokyo, osaka, kyoto, fukuoka, hokkaido, aichi …
3. Set Max restaurants (Gurunavi pages 30 at a time)
4. Enable Include detail page data when you need phone numbers, addresses and opening hours
5. Run, then download from the Dataset tab as JSON / CSV / Excel, or fetch through the Apify API

Example input

{
  "keyword": "焼肉",
  "prefecture": "osaka",
  "maxItems": 300,
  "includeDetails": true
}

Notes on reliability

• List data comes from the same structured payload Gurunavi's own site renders from, and detail data from the restaurant's schema.org block — both far steadier than scraping styled markup
• Requests are paced with backoff and retries, and results are de-duplicated by shop number across pages, so you never pay twice for the same restaurant
• The Actor stops by itself once Gurunavi stops returning new venues

Pricing model

You pay per result — a small fee for each restaurant returned. You only pay for rows you actually receive.

FAQ

Does it need a proxy? No. It runs from Apify's servers without residential proxies.

Are phone numbers always present? They come from the restaurant's own listing, so nearly all member venues publish one. Non-member listings occasionally omit it, in which case the field is empty rather than wrong.

Can I export a whole city? Yes — leave the keyword empty, pick the area slug and raise maxItems. The log prints Gurunavi's total match count first, so you can see the size of the job before committing.

How is this different from a Tabelog scraper? Different directory, different venue mix. Gurunavi skews toward member restaurants that publish structured budget and contact details, which makes it the better source when you need phone numbers and price levels rather than user reviews.