OpenRice Restaurant Scraper (Hong Kong)

Structured restaurant data from OpenRice Hong Kong — full restaurant detail, reviews, and menu photos — delivered to an Apify dataset you can export as JSON, CSV, or Excel, or pull via the API.

⏱️ This is a scheduled batch data feed, not a real-time lookup tool. OpenRice has no public API and actively rate-limits scrapers, so this actor crawls politely and slowly on purpose (~1 restaurant every 10–15 seconds) to stay reliable instead of getting blocked. A handful of restaurants takes minutes; a large crawl runs for hours. Run it on a schedule and collect the dataset — don't expect instant results. This trade-off is what keeps the data flowing.

---

What you get per restaurant

Every record is built from OpenRice's own data — no field is invented; anything the source doesn't provide is left empty rather than guessed.

• Identity & location — name (and other-language name), address, district, region, latitude/longitude, phone(s), website
• Ratings & signals — overall score, smile/cry counts, review count, photo count, bookmark count, price range, open-since, Michelin/award text
• Categories — cuisine / dish / amenity tags
• Opening hours
• Reviews — the most relevant + recent reviews (up to 50 per restaurant), each with rating, text, and photo URLs
• Photos — door/cover photo and menu photos (CDN image URLs)

See the Output tab for the full field list and a sample record.

Input

Choose what to crawl. Filters combine (e.g. District + Cuisine + Keyword narrow together). If you provide Restaurant IDs or Start URLs, those win and the filters are ignored.

Filters (combine; leave all empty + tick "Crawl all" for everything):

Field	Description
District	Pick a Hong Kong district (covers all main dining areas — TST, Causeway Bay, Mong Kok, Central, Wan Chai, Kwun Tong, …).
Keyword	Free-text search — restaurant name, cuisine, dish, or area.
Cuisine ID	OpenRice cuisine/category id (advanced — raw numeric id).
Newly opened only	Restrict to newly-opened restaurants (~900).
Crawl all of Hong Kong	Everything (~33,000) when no filter is set, bounded by Max restaurants.

Target specific restaurants instead (overrides filters):

Field	Description
Restaurant IDs	OpenRice POI ids — the number after -r in a URL (e.g. 600214).
Start URLs	OpenRice restaurant detail page URLs.

If you set nothing at all, the actor defaults to newly opened only.

Tuning (applies to every mode):

Field	Default	Description
Max restaurants	500	Hard cap per run — guards runtime and proxy usage.
Reviews per restaurant	50	Most relevant + recent reviews to collect. 0 skips reviews.
Include menu photos	on	Collect user-uploaded menu / price-list photos. Turn off to go faster.
Language	zh	zh (Chinese) or en (English).

How to use it (recommended pattern)

1. Pick a District (or a Keyword), set a sensible Max restaurants cap.
2. Schedule the actor (e.g. daily or weekly) under Schedules so the data stays fresh automatically.
3. Read results from the dataset — export to JSON/CSV/Excel or fetch via the Apify API / integrations (Make, Zapier, webhooks).

💡 A full Hong Kong crawl is tens of thousands of restaurants and runs for hours. Start with a modest Max restaurants cap, confirm the data looks right, then raise it and run on a schedule.

Requirements

⚠️ This actor needs Apify Residential Proxy (OpenRice HK is geo-gated and defended — datacenter IPs are blocked). Residential proxy is included on Apify's paid plans (Starter and above). On the free plan the crawl will be blocked. The actor runs on your account and uses your proxy, so usage (proxy + compute, ~tens of US$ per thousand restaurants) is billed to you by Apify.

Pricing

This actor is offered as a flat monthly rental — pay once per month for unlimited runs. (Apify platform usage — proxy + compute — is billed separately to your account, as with any actor. See the requirements above.)

Honest limitations

We'd rather you know these up front than be surprised:

• Requires a paid Apify plan (for Residential proxy — see Requirements).
• Hong Kong only. OpenRice HK is geo-gated; this actor targets HK restaurants.
• Built for scheduled batch use. Large crawls take hours by design (see the note above). If you need sub-second single lookups, this isn't the right tool.
• popular_dishes is intentionally empty. OpenRice's current data no longer exposes structured dish-name tags, so we return the real menu photos and leave the dish list empty rather than fabricate groupings from free-text captions.
• Depends on OpenRice's site. If OpenRice changes their site we patch the actor as fast as we can, but a run during a change may return fewer fields.

Support

Found a broken field or have a request? Use the Issues tab on this actor — we monitor it and ship fixes.