OpenTable Scraper: Restaurant Menus, Ratings, and Availability
OpenTable restaurant pages are location-sensitive: menus, price tiers, ratings, and reservation windows can change by city and by page.
This scraper page describes a single-call API that renders the page, rotates residential proxies, and returns HTML or parsed JSON. Use it when you need repeatable restaurant data collection without maintaining your own headless browser fleet.
What an OpenTable request can return
A request against an OpenTable restaurant or menu URL goes through the renderer, which executes the page's JavaScript, and comes back as rendered HTML ready to parse. When you supply extraction rules, the response can instead come back as parsed JSON.
Fields the page maps for a typical restaurant page include:
- Restaurant name
- Location
- Cuisine
- Price tier
- Rating
- Review count
- Menu items
- Reservation availability windows
If you only need the rendered page, you can skip extraction rules and parse the HTML yourself. If you want a stable field shape, define it with CSS selectors or a natural-language AI spec.
Request options and when to use them
Four advanced parameters matter most for OpenTable work. They are not all required; add them when the page or target behavior calls for them.
- render_js — enables JavaScript rendering. The renderer executes the page's JS, so reach for this option when the content you need is client-rendered.
- stealth_proxy — used for CAPTCHA-heavy targets. Listed as the option for CAPTCHAs.
- country_code — routes the request through a residential IP in the specified country. Use it when menus or availability differ by geography.
- ai_extract_rules — a natural-language extraction spec. Use it when you want field-level JSON without writing CSS selectors.
A separate option, extract_rules, maps CSS selectors to field names for deterministic JSON output. XPath extraction rules are also mentioned in the plan comparison.
A practical rule: start with rendered HTML and inspect it. If the field shape is stable, move to extract_rules. If the page changes often or the fields are hard to select, try ai_extract_rules.
Three common OpenTable workflows
Three recurring workflows each have a different data shape and a different tolerance for page changes.
Restaurant menus. Menu data is useful for market and competitor analysis: what dishes appear, how menus are structured, and how offerings differ by location. Because menus are often location-locked, pair this workflow with country_code when you need a specific market.
Reservation availability. Availability windows are useful for lead generation and positioning: which time slots are open, how far ahead they are bookable, and how competitor availability compares. Availability is time-sensitive, so schedule collection close to when you need the data rather than relying on a stale snapshot.
Customer feedback. Ratings and review counts support theme and pain-point analysis. Treat review text as user-generated content and check that your use complies with the target site's terms and applicable privacy rules before collecting it at scale.
Credit costs and plan fit
Requests consume API credits. The per-request figures are:
- Base request: starts at 1 credit.
- JavaScript rendering: 5 credits per successful request with JS rendering enabled.
- Premium proxy: 10 credits without JS rendering, 25 credits with JS rendering.
- stealth_proxy: 75 credits.
Credits are valid for one month and do not roll over. Concurrency is the number of requests that can be sent at the same time; it is set per plan rather than per target.
A worked example: a batch of 1,000 OpenTable pages rendered with JavaScript and routed through a premium proxy would consume 25,000 credits (1,000 × 25). The same batch with stealth_proxy would consume 75,000 credits. Check the current plan table before sizing a run, because the figures above are the captured reference values and plan allowances can change.
The plan comparison below preserves every tier, price, credit allowance, concurrency limit, and feature inclusion exactly as captured. Use it to match a monthly volume to a tier, then confirm current pricing before purchase.
Plan comparison
The following table is the captured plan reference. Prices are exclusive of VAT. Startup and Enterprise 41 are marked as recommended tiers; that is the publisher's recommendation, not a performance claim. Treat all figures as a dated reference and verify current pricing and allowances before subscribing.
Telling failure modes apart
Not every failed request means the same thing. Three situations are easy to conflate:
- Concurrency limits. The API enforces concurrency per plan, not a per-target rate limit. If you exceed your plan's concurrent request allowance, slow down or move to a higher tier.
- Target throttling. OpenTable may throttle aggressive request patterns. Space out requests or use multiple sessions. This is a target-side behavior, not an API-side rate limit.
- CAPTCHA or anti-bot response. If the page returns a challenge, stealth_proxy is the option to reach for. That option costs more credits, so use it only where needed.
A useful diagnostic order: check your concurrency setting first, then request spacing, then whether the response is a challenge page. Changing proxy mode before checking the first two can waste credits.
Setup path
Getting from zero to a first OpenTable response takes four steps:
- Create an account to get an API key and the free starting credits.
- Install an SDK if you want one. Python, Node.js, Go, PHP, Ruby, and Java SDKs are available, and plain cURL works too.
- Send a GET request with your API key and an OpenTable URL on opentable.com.
- Add advanced parameters only when the page needs them: render_js, stealth_proxy, country_code, or ai_extract_rules.
Code examples are published in Python, Node.js, cURL, and a request builder. If your stack is not listed, use cURL or any HTTP client and send the same request shape.
Data handling and compliance
The service does not collect or store personal data from scraped sites unless the user explicitly requests it. That is a statement about the service's handling, not a blanket permission to collect personal data from OpenTable. Review text and reviewer identifiers can be personal data under GDPR or CCPA depending on jurisdiction and context. Before collecting reviews at scale, confirm your legal basis, minimize what you store, and check OpenTable's terms and robots guidance.
| Plan | Price / month | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
All prices are exclusive of VAT. Figures are the captured reference values and may change; verify current pricing and allowances before subscribing.
Frequently asked questions
Do I need an OpenTable account to use the scraper?
No external OpenTable account is required. You sign up for an API key, send the OpenTable URL, and the service handles rendering and proxy rotation. The source offers 1,000 free credits at signup with no card required.
Can I target a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when menus or availability differ by geography.
Is there a rate limit per OpenTable target?
The API enforces concurrency limits per plan rather than a per-target rate limit. If OpenTable throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON instead of HTML?
There are two routes. With extract_rules you map CSS selectors to the field names you want, giving a deterministic shape. With ai_extract_rules you describe the fields in plain language and let the AI layer resolve them. Either way, the response arrives as parsed JSON rather than raw HTML.
Which languages can I use?
Any language that can send an HTTP request. The source publishes SDKs for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.
How much does it cost per request?
Base requests start at 1 credit. JavaScript rendering costs 5 credits per successful request. Premium proxies cost 10 credits without JS rendering or 25 with it. stealth_proxy costs 75 credits. Credits are valid for one month and do not roll over. The source offers 1,000 free credits at signup; paid plans start at $19/month.