opentable.com API: batch_availability
www.opentable.com via Parse · food_dining
Batch-resolve restaurant names by city and check availability for each. For each {name, city} pair, searches OpenTable to find the best-matching restaurant, then checks availability for all resolved restaurants in one batch call. Returns each input mapped to its resolved restaurant details (name, restaurant_id, address, cuisine, rating) and available time slots. Makes N+1 upstream round-trips (one search per input pair plus one batch availability call). Unresolved pairs appear with resolved=false and empty availability. Search for restaurants, get autocomplete suggestions, resolve locations, and check availability on OpenTable. Covers the US market with rich restaurant data including ratings, reviews, photos, pricing, and features. Fulfilled by Parse from www.opentable.com.
- food-dining
- maps-geo
- parse
- platform-key
- travel
- www-opentable-com
Price and execution
- Price
- $0.02 USD credits / call
- Trust tier
- Verified
- Execution
- Managed call
- Capability group
- food_dining
Interface snapshot
- Protocol
- HTTP operation
- Operation
- POST /scraper/f37010d4-cf53-464e-8c5a-8b0fb742720e/batch_availability
- Interface artifact
- sha256:2cc216a1c56796556ebdc577aa33d8aad1cebc9b053217e256c2c7c64b7ab925
- Manifest digest
- sha256:c7898cda4a4d82be9cb507ed7a84086f9a3d121b95f3c3917abdeab15c10758c
Request fields
- date (string): Date in YYYY-MM-DD format. Defaults to tomorrow.
- time (string): Time in HH:MM format (24h)
- party_size (integer): Number of diners
- restaurants (string, required): JSON array of objects, each with 'name' (required) and 'city' (optional) fields, e.g. [{"name": "Nobu", "city": "New York"}, {"name": "Alinea", "city": "Chicago"}]
Example queries
- {"date":"2026-08-26","time":"19:00","party_size":"2","restaurants":"[{\"name\": \"Nobu\", \"city\": \"New York\"}]"}