Restaurant availability and reservation monitoring
Use OpenTable endpoints to turn restaurant availability and reservation monitoring into repeatable API requests with documented inputs and JSON responses.
Turn public OpenTable mobile app data into structured dining data — restaurant profile, cuisines, hours, and price band with real-time bookable timeslots for a date/time and party size, diner reviews with per-category ratings, full menus, and free-text restaurant search near a location. Credential-free.
Extract OpenTable restaurant profiles with live bookable timeslots, diner reviews, menus, and location-based restaurant search as structured JSON.
Endpoint families
2
Documented params
17
Examples
4
Live catalog snapshot
Active endpoints
4
Methods
GET
Required params
10
Schema refs
4
{
"platform": "OpenTable",
"endpoint": "opentable-search",
"method": "GET",
"path": "/opentable/search",
"auth": "apiKey"
}Use cases
Extract OpenTable restaurant profiles with live bookable timeslots, diner reviews, menus, and location-based restaurant search as structured JSON.
Use OpenTable endpoints to turn restaurant availability and reservation monitoring into repeatable API requests with documented inputs and JSON responses.
Use OpenTable endpoints to turn diner review and rating analytics into repeatable API requests with documented inputs and JSON responses.
Use OpenTable endpoints to turn menu and price tracking into repeatable API requests with documented inputs and JSON responses.
Use OpenTable endpoints to turn location-based restaurant discovery into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live OpenTable endpoint catalog — 4 endpoints, 17 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
4 documented OpenTable endpoints, grouped into 2 request families — Restaurant and Search.
17 request parameters are documented across those OpenTable endpoints, 10 of them required — the full input contract is public before you write any integration code.
4 of the 4 OpenTable endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
OpenTable endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
4 hosted MCP tools back the OpenTable endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/opentable/restaurant
/opentable/search
Endpoint catalog
/opentable/searchSearches restaurants by free-text term (cuisine, name, neighborhood) near a latitude/longitude, for a given date/time and party size, including inline live availability per result. Credential-free.
MCP tool opentable_search
/opentable/restaurantReturns a restaurant's profile (location, cuisines, hours, price band, review summary) plus real-time bookable timeslots for the given date/time and party size. Credential-free.
MCP tool opentable_restaurant
/opentable/restaurant/reviewsReturns a page of diner reviews (author, text, per-category ratings) for a restaurant. Credential-free.
MCP tool opentable_restaurant_reviews
/opentable/restaurant/menusReturns a restaurant's menus (sections, items, prices). Credential-free.
MCP tool opentable_restaurant_menus
Related APIs
Travel & Hospitality
Build travel and lodging research workflows from structured Airbnb stay, room, availability, and review data.
Travel & Hospitality
Research hotels, restaurants, attractions, and destination pages from TripAdvisor with normalized listing and review endpoints.
Travel & Hospitality
Turn Expedia's Stays, Flights, and Things To Do results into structured JSON — destination search, hotel listings with pricing and reviews, flight offers, and activity search, sourced from the same API the official mobile app uses. Credential-free.
Company coverage
Booking Holdings Inc. · BKNG
OpenTable is operated by Booking Holdings Inc. (BKNG). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the OpenTable endpoints above.
Other Booking Holdings Inc. platforms in the catalog
How to scrape OpenTable
OpenTable surfaces restaurant profiles, live availability, reviews, and menus through its mobile app's anonymous guest API. Crawlora's OpenTable endpoints return restaurant detail with inline bookable timeslots, diner reviews, menus, and free-text search results as normalized JSON — no account or caller-supplied token.
Search by free-text term (cuisine, name, neighborhood) near a latitude/longitude, or use a known restaurant ID.
Pass parameters to /opentable/restaurant, /opentable/restaurant/reviews, /opentable/restaurant/menus, or /opentable/search.
Receive restaurant profile and location data, live bookable timeslots for a date/time and party size, diner reviews with per-category ratings, or full menu sections and items.
Feed availability dashboards and AI pipelines, or re-run to track reservation availability, ratings, and menu prices over time.
FAQ
Send a restaurant ID or a search term with a latitude/longitude to Crawlora's OpenTable endpoints and get restaurant profiles, live bookable timeslots, diner reviews, and menus as structured JSON — no account.
Yes. /opentable/restaurant returns real-time bookable timeslots inline when you pass a date/time and party size, and /opentable/search returns the same live availability per result.
Collecting publicly accessible restaurant, menu, review, and search data is generally permissible if you respect OpenTable's terms of use, robots directives, rate limits, and applicable law.