Wire it up. See the schema.
- 100 free requests on signup
- Every endpoint included
- No credit card required
- Same schema as paid
A quick demo might save your team weeks of engineering work.
Resources
Free Tools
Pull restaurants by location, cuisine, price band, rating, address, and private dining venues from OpenTable as clean JSON.
curl "https://api.stayapi.com/v1/opentable/search" \ -G \ -H "x-api-key: $STAYAPI_KEY" \ -d "latitude=34.0634" \ -d "longitude=-118.2806" \ -d "date=2026-06-23" \ -d "time=19:00" \ -d "party_size=2" \ -d "prices=[2, 3]"
curl "https://api.stayapi.com/v1/opentable/private-dining" \ -G \ -H "x-api-key: $STAYAPI_KEY" \ -d "latitude=32.8959" \ -d "longitude=-97.0671" \ -d "min_capacity=100" \ -d "with_facets=true"
{
"success": true,
"total": 250,
"restaurants": [
{
"id": 67720,
"name": "Perch LA",
"url": "https://www.opentable.com/perch",
"primary_cuisine": "French American",
"dining_style": "Casual Elegant",
"price_band": {
"id": 3,
"name": "$31 to $50",
"currency_symbol": "$"
},
"rating": 4.5,
"review_count": 12360,
"neighborhood": "Downtown",
"phone": "(213) 802-1770",
"has_private_dining": true
}
]
}
{
"success": true,
"total": 117,
"server_total": 178,
"restaurants": [
{
"id": 1331095,
"name": "Soy Cowboy",
"primary_cuisine": "Pan-Asian",
"price_band": {
"id": 3,
"name": "$31 to $50",
"currency_symbol": "$"
},
"rating": 4.6,
"neighborhood": "Arlington",
"is_instant_bookable": true,
"space_count": 4,
"private_dining": {
"contact": "The Sales Event Manager",
"phone": "(713) 804-3317",
"email": "events@example.com",
"largest_capacity": 200
}
}
]
}
Trusted by hospitality teams at
OpenTable has no public data API for the restaurant listings and private dining venues that product and research teams actually need. The usual answer is a scraping stack: headless browsers, rotating proxies, a GraphQL gateway to reverse, and a parser that breaks every time the page changes.
StayAPI is that layer, run for you. You send coordinates with a reservation date, time, and party size, and get structured JSON back: restaurant name, cuisine, price band, guest rating, photos, structured address, phone, and feature flags. Ask for private dining and you also get the event contact, largest space capacity, and instant book flag. The same data, the same shape, on every call.
x-api-key in, JSON out. Restaurant search and private dining behind one base URL. No SDK to install.
Fetching, parsing, proxy rotation, and source uptime are ours. You consume normalized dining JSON and never touch the OpenTable GraphQL gateway.
Every call hits OpenTable live, so cuisine, ratings, and private dining contacts are current to the request, not a stale nightly snapshot.
Each returns normalized JSON in the same shape. Click any endpoint for parameters, an example response, and a live playground.
The same endpoints, pointed at different jobs. These are the ones we see most.
Power a dining search experience with live OpenTable restaurants by location and date: cuisine, price band, rating, neighborhood, and photos in one response.
Surface venues that host private events near a place, ranked by largest space capacity, with the event contact name, phone, and email ready to reach out.
Benchmark a restaurant against nearby venues on rating, review count, price band, and recent reservation volume using the same fields for every listing.
Feed structured OpenTable restaurant and private dining data into an LLM tool call so your agent recommends from live listings, not stale embeddings.
Flat monthly plans, every endpoint included on every plan. 1 request = 1 credit. No per-endpoint multipliers, no surprise overages.
Wire it up. See the schema.
Kick the tires in production.
Small prod workloads and growing apps.
Daily pulls in production.
Above 100k / month, annual terms, white-glove onboarding.
Every plan ships every endpoint. Same uptime, same schema, same response time.
Don't see your question? Email us at info@stayapi.com.
OpenTable runs partner and affiliate programs for restaurants and connectivity, but there is no open public API for pulling restaurant listings, cuisine, ratings, or private dining venues. StayAPI gives you that data over plain REST with a key you get in 30 seconds.
Call /v1/opentable/search with a latitude, longitude, date, and time. You get matching restaurants with cuisine, price band, rating, address, phone, photos, and feature flags as JSON. See the restaurant search endpoint docs.
Yes. /v1/opentable/private-dining returns venues that host private events near your coordinates, each with the event contact name, phone, email, largest space capacity, and an instant book flag. Filter by min_capacity to match your party. See the private dining endpoint docs.
You get 100 free requests on signup, every endpoint included, no credit card. After that it is flat monthly plans starting at $49. One request equals one credit, with no per-endpoint multipliers.
Both end with live OpenTable data in your stack. The fast path is on the left.
100 free requests after sign up. Fastest way to see if the schema fits.
Start free15 minutes. Volume + endpoint mix. Walk out with a quote.
Book a demo