OpenTable Restaurants, Ratings & Reviews Scraper
Pricing
from $5.00 / 1,000 restaurant scrapeds
OpenTable Restaurants, Ratings & Reviews Scraper
Scrape OpenTable restaurants in any city. Export profiles, ratings, reviews, cuisines, prices, hours, and coordinates as structured JSON. MCP-ready.
Pricing
from $5.00 / 1,000 restaurant scrapeds
Rating
0.0
(0)
Developer
Muhammad Afzal
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Scrape OpenTable restaurants in any city. Export profiles, ratings, reviews, menus, cuisine, price, hours, and coordinates as structured JSON, CSV, or Excel. MCP-ready for AI agents.
Features
- Search by city, cuisine, neighborhood, or restaurant name — paginate through all OpenTable search results
- Scrape by direct URL — paste any OpenTable restaurant profile URL
- Full restaurant profiles — name, description, overall rating, review counts, cuisines, price tier, address, coordinates, neighborhood, metro, phone, website, hours, dining style, dress code, parking, executive chef, features (bar, counter, outdoor, high-top, max party size), private dining, takeout, delivery, payment options, gallery photos
- Optional reviews extraction — collect individual reviews with full text, diner profiles (name, initials, location, VIP status, review count), dined/submitted dates, and helpfulness votes
- Browser-based anti-bot bypass — uses Playwright with Chromium + response interception to capture OpenTable's API responses with correct TLS fingerprints, defeating Akamai protection
- MCP-ready — optimized for Claude, ChatGPT, Cursor, and other AI agents with semantic field names and structured output
Use Cases
- Competitive analysis and benchmarking of nearby restaurants (ratings, amenities, price band)
- Market-entry research and city-level restaurant coverage studies
- Restaurant scoring, ranking, and neighborhood food-density analysis
- Review monitoring and sentiment analysis
- Sourcing acquisition or M&A targets using reservation counts and review velocity
- Enriching travel apps, directories, and restaurant profile databases with geocoordinates
- Building city guides, affiliate booking pages, and editorial "best of" lists
- Generating prospect lists and CRM enrichment for sales outreach
- Training recommendation models and AI prototypes on real restaurant attributes
Input
The actor supports two input modes (can be combined):
Search Terms
Provide city names, neighborhoods, cuisines, or restaurant names:
{"searchTerms": ["New York", "Italian Chicago", "sushi San Francisco"],"maxResults": 500,"includeReviews": false}
Direct URLs
Provide specific OpenTable restaurant URLs:
{"startUrls": [{ "url": "https://www.opentable.com/r/le-bernardin-new-york" },{ "url": "https://www.opentable.com/restaurant/profile/100" }],"includeReviews": true,"maxReviewsPerRestaurant": 50}
All Input Fields
| Field | Type | Default | Description |
|---|---|---|---|
searchTerms | array | ["New York"] | City, neighborhood, cuisine, or restaurant names to search |
startUrls | array | [] | Direct OpenTable restaurant URLs |
maxResults | integer | 100 | Max restaurant records to return |
priceBands | array | [] | Filter by price tier (1-4) |
sortBy | string | web_conversion | Sort order: web_conversion (featured) or distance |
includeReviews | boolean | false | Also scrape individual reviews |
maxReviewsPerRestaurant | integer | 50 | Max reviews per restaurant |
proxyConfiguration | object | Apify Proxy | Proxy routing (residential recommended) |
Output
Each record contains:
| Field | Type | Description |
|---|---|---|
name | string | Restaurant name |
url | string | OpenTable profile URL |
restaurantId | number | OpenTable internal ID |
description | string | Restaurant description |
rating | number | Overall rating (1-5) |
reviewCount | number | Recent review count |
totalReviewCount | number | Total reviews |
primaryCuisine | string | Primary cuisine |
cuisines | string[] | All cuisine tags |
priceTier | number | Price band (1-4) |
priceRange | string | Price label |
address | object | Full postal address |
latitude | number | Geocode |
longitude | number | Geocode |
neighborhood | string | Neighborhood |
metro | string | Metro area |
phoneNumber | string | Contact phone |
website | string | Restaurant website |
hoursOfOperation | string | Hours text |
diningStyle | string | Dining style |
dressCode | string | Dress code |
parkingInfo | string | Parking details |
executiveChef | string | Chef name |
imageUrl | string | Cover photo URL |
features | object | Bar, counter, outdoor, highTop, maxPartySize |
hasPrivateDining | boolean | Private dining available |
hasTakeout | boolean | Takeout available |
paymentOptions | string[] | Accepted payments |
photoUrls | string[] | Gallery photos |
reviews | array | Individual reviews (if enabled) |
scrapedAt | string | ISO timestamp |
sourceUrl | string | Source URL |
Review Object (when includeReviews is true)
| Field | Type | Description |
|---|---|---|
reviewId | string | Unique review ID |
text | string | Full review text |
dinedDate | string | Dine-in date (ISO) |
submittedDate | string | Submission date (ISO) |
ratingOverall | number | Overall rating |
reviewerName | string | Diner nickname |
reviewerInitials | string | Diner initials |
reviewerLocation | string | Diner city |
reviewerIsVip | boolean | VIP status |
reviewerApprovedReviewCount | number | Diner's total reviews |
reviewHelpfulUp | number | Helpful up-votes |
reviewHelpfulDown | number | Helpful down-votes |
Pricing
This actor uses Pay-Per-Event pricing:
| Event | Price | Description |
|---|---|---|
| Restaurant scraped | $0.005 | Per restaurant record returned |
| Review scraped | $0.001 | Per review returned (only when includeReviews is enabled) |
| Actor start | $0.00005 | Per run start (memory-based) |
Example costs:
- 100 restaurants, no reviews: ~$0.50
- 100 restaurants with 50 reviews each (5,000 reviews): ~$5.50 ($0.50 + $5.00)
- 1,000 restaurants, no reviews: ~$5.00
How It Works
The actor uses a 3-layer extraction strategy to maximize reliability against OpenTable's Akamai protection:
- Response interception (primary) — Playwright's
page.on('response')captures OpenTable's own API JSON responses with correct TLS fingerprints and auth headers - Embedded JSON extraction (fallback) — parses
window.__NEXT_DATA__and<script type="application/json">SSR hydration data - DOM parsing (last resort) — multi-selector fallback extraction from rendered HTML
Technical Details
- Crawler: PlaywrightCrawler with Chromium launcher
- Anti-bot: Browser-based with response interception, randomized viewports, random delays, session pooling
- Proxy: Apify Proxy (datacenter default, residential recommended for blocked regions)
- Language: TypeScript
- Output: Structured JSON dataset (exportable as CSV, Excel, JSON, XML via Apify Console)
Export Scraped Data
Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools via the Apify platform. Results can be downloaded as JSON, CSV, Excel, or XML from the Apify Console.
API Usage
# Run via APIcurl -X POST "https://api.apify.com/v2/acts/USERNAME~opentable-scraper/runs?token=YOUR_TOKEN" \-H "Content-Type: application/json" \-d '{"searchTerms": ["New York"], "maxResults": 100}'
// Run via JavaScript SDKimport { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'YOUR_TOKEN' });const run = await client.actor('USERNAME/opentable-scraper').call({searchTerms: ['New York'],maxResults: 100});const dataset = await client.dataset(run.defaultDatasetId);const items = await dataset.listItems();
Limitations
- OpenTable uses Akamai protection — residential proxies may be required for some regions
- Free users are limited to 10 results per run
- Review extraction adds significant time per restaurant
- Some fields may be null if OpenTable doesn't provide them for a given restaurant
Support
If you encounter issues, please report them on the Issues tab in the Apify Console.