OpenTable

Collect restaurants, ratings and reservation availability from OpenTable. Search one location or a list and choose the date, time and party size.

Features

Process	What you get
Search suggestions	Matching locations and restaurants with available IDs and coordinates
Restaurant search	Available names, addresses, cuisines, price bands, ratings, photos and profile links
Availability	Available reservation times and booking links

Availability reflects the selected date and party size. Restaurant fields and supported filters depend on the source response.

Quick start

{
  "process": "gr",
  "query": "Boston",
  "maximum": 50,
  "country": "com"
}

Choose gs for search suggestions, gr for restaurants or ga for availability. For multiple searches, supply queries, such as ["Boston", "Chicago"]; this list replaces query.

For availability, set date in YYYY-MM-DD format, time such as 19:00, and people. If the date is omitted, the actor uses two days from today. Times are local to the restaurant. An exact restaurant name targets that restaurant when OpenTable finds a matching listing.

maximum limits results per query. maxResults limits real results across the run. Restaurant search continues through available pages until the limit is reached or OpenTable has no more results.

Results

Search suggestions and restaurant results preserve OpenTable's fields. Availability returns one row per restaurant/day with slots and a sorted summary containing available times, booking links and slot types. availableDate on a slot accounts for times crossing midnight.

Availability is a snapshot and may change before you book. Booking links open OpenTable; this actor does not make reservations. Coverage and available fields vary by country and restaurant.

Search tips

Choose the OpenTable country domain that covers your destination. Use search suggestions to identify how OpenTable names a location. Narrow filters may return fewer results than requested.

Direct connections are used by default. OpenTable may restrict availability requests, including through proxies. If access is blocked, try another proxy or retry later. For support, share the run URL and the affected query.

Pricing

Each valid pay-per-event run with at least one input includes a shared minimum charge of 100 restaurant result units. Results above 100 are charged individually at the Pricing tab rate, plus the listed $0.01 start fee. The minimum also applies when fewer results are returned or no matches are found. Clearly marked placeholder rows contain no scraped restaurant data; filter them out when exporting. Each separate run has its own minimum, including scheduled or API runs. Platform usage is included. Set a maximum run budget of at least $0.04.

Unsuccessful lookups

Where listed in the Pricing tab, a handled lookup problem that prevents a run from returning any real results produces one clear error record and a single $0.02 unsuccessful-lookup fee, in addition to any listed start fee.