Retty Japan Restaurant Scraper avatar

Retty Japan Restaurant Scraper

Pricing

from $3.40 / 1,000 results

Go to Apify Store
Retty Japan Restaurant Scraper

Retty Japan Restaurant Scraper

Scrape restaurant data from Retty (レッティ), Japan's largest real-name restaurant review service with 700,000+ listings. Names, genres, budgets, match scores, stations, addresses, coordinates, phone numbers, hours, seating and amenities across all 47 prefectures. HTTP-only, no API key required.

Pricing

from $3.40 / 1,000 results

Rating

0.0

(0)

Developer

Piquno

Piquno

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 days ago

Last modified

Categories

Share

Scrape restaurant data from Retty (レッティ), Japan's largest real-name restaurant review service, covering 700,000+ restaurants across all 47 prefectures. Get names, genres, lunch and dinner budgets, Retty match scores, nearest stations, and, with detail pages enabled, full addresses, GPS coordinates, phone numbers, opening hours, closed days, seating, private rooms, smoking policy, accepted cards and ratings.

HTTP-only. No browser, no API key, no login.

Why Retty

Retty sits alongside Tabelog and HotPepper Gourmet as one of Japan's three major restaurant platforms, but with a different signal: reviews are tied to real, named users, and each restaurant carries a match score and an Excellent / Good / Average recommendation breakdown rather than an anonymous star average. That makes it a useful third source for:

  • Market research and site selection: restaurant density, genre mix and budget bands by area
  • Location intelligence: coordinates and station access for every venue
  • Lead generation: phone numbers, websites and reservation availability for restaurant-facing businesses
  • Travel and food apps: budgets, hours, private rooms and payment methods in a clean schema
  • Cross-platform matching: join with Tabelog and HotPepper data by name, phone or coordinates

How it works

Retty does not expose a paginated search. Instead it publishes curated "top 20" lists for every sub-area, and again for every genre, occasion and theme within that sub-area. This Actor walks that lattice, collects the restaurant cards from each list, and deduplicates by restaurant ID, so a Tokyo run across all sub-areas and genres yields thousands of unique restaurants rather than twenty.

You control how wide it goes with Crawl depth:

ModeWhat it readsRough yield
Areas onlyOne list per area~20 per area
Sub-areasOne list per sub-area~20 per sub-area
Sub-areas + genres (default)Every genre list per sub-areaHundreds per area
FullGenres + occasions + themed listsWidest coverage

Restaurants are pushed to the dataset as each list is parsed, so you are charged only for what is actually delivered, and a run that stops early still returns everything it found.

Input

FieldDescription
PrefectureAny of the 47 prefectures. Defaults to Tokyo.
AreaOptional. An area name substring as shown on Retty (新宿, 渋谷, 銀座) or an ARE code. Blank scrapes the whole prefecture.
Sub-areaOptional. Narrow further by name (歌舞伎町) or SUB code.
GenreOptional. One cuisine, e.g. Izakaya, Sushi, Ramen, Yakiniku, Cafe. Leave as Any to crawl all genres.
Custom category codeAdvanced. Any LCATx/CATy path for a genre not in the list.
Crawl depthSee table above.
Start URLsAdvanced. Paste any Retty list URLs to scrape directly; overrides the fields above.
Max resultsStop after this many unique restaurants.
Include detail pagesFetch each restaurant's page for the full address, coordinates, phone, hours, seats and rating. One extra request per restaurant.
Delay / ConcurrencyPoliteness controls. Defaults are conservative.

Example, 200 izakaya in Shinjuku with full details:

{
"prefecture": "13",
"area": "新宿",
"genre": "LCAT1/CAT350",
"maxResults": 200,
"includeDetails": true
}

Output

One item per restaurant. Listing-card fields are always present; detail fields appear when Include detail pages is on.

{
"restaurantId": "100001455698",
"name": "肉バル肉ブーケ&チーズ食べ飲み放題 個室 Meat StanD 新宿東口店",
"url": "https://retty.me/area/PRE13/ARE1/SUB101/100001455698/",
"station": "西武新宿駅",
"walkMinutes": 2,
"genres": ["居酒屋", "イタリアンバル", "肉バル"],
"dinnerBudget": "〜3,000円",
"lunchBudget": "〜2,000円",
"matchScore": 4.45,
"payPayAccepted": true,
"onlineReservation": true,
"isPromoted": false,
"photo": "https://ximg.retty.me/crop/s524x524/q80/das/-/retty/img_ebisu/restaurant/100001455698/archive/....jpg",
"prefectureCode": "PRE13",
"areaCode": "ARE1",
"subAreaCode": "SUB101",
"address": "東京都新宿区歌舞伎町1-17-6 アツミビル3F",
"postalCode": "1600021",
"latitude": 35.694295,
"longitude": 139.7013186,
"phone": "050-5262-1077",
"phoneDirect": "03-6636-4386",
"rating": 4.4,
"reviewCount": 14,
"wentCount": 17,
"recommendExcellent": 13,
"recommendGood": 3,
"recommendAverage": 1,
"hours": "[全日] 12:00 〜 24:00 L.O. 23:30",
"closedDays": "無休 年末年始(要確認)",
"totalSeats": "70席",
"privateRoom": "有 2人用 4人用 6人用 7人以上用",
"smoking": "全席喫煙可",
"creditCards": ["VISA", "Mastercard", "Amex", "Diners", "JCB"],
"qrPayments": ["PayPay"],
"wifi": "有",
"homepage": ["https://meat-stand.owst.jp/"],
"lastReviewDate": "2026-09-04"
}

The Output tab offers three views: Overview, Location & contact, and Facilities. Export to JSON, CSV or Excel as usual.

What this Actor does not collect

Only restaurant business information that Retty publishes on each listing. It does not collect review text, reviewer names, profiles or any other user content. Aggregate counts (rating, review count, recommendation breakdown) are included.

Tips

  • Start with Sub-areas depth and a small Max results to check an area, then widen.
  • For a whole-prefecture pull, leave Area blank and set Max results generously; deduplication keeps the count honest.
  • Include detail pages roughly doubles request count. Turn it on only when you need addresses, coordinates or hours.
  • Restaurant IDs are stable. Re-run on a schedule and diff on restaurantId to track new openings.

Same author, same schema conventions, so the three join cleanly:

Support

Found a page that doesn't parse, or need a field that isn't here? Open an issue on the Actor's Issues tab and include the Retty URL.

Unofficial. Not affiliated with Retty, Inc.