Resolve any OpenTable restaurant profile or city search into clean JSON: reservation availability and time slots, dining menus, price bands, diner ratings, and ranked results — not delivery, but the full reservations layer.
OpenTable is a restaurant-reservation network rather than a delivery marketplace, surfacing bookable time slots, dining menus, and diner reviews for restaurants across many markets. The OpenTable Scraper API resolves restaurant profiles and city searches into validated JSON covering availability, menus, and review streams.
It is built for hospitality-intelligence and demand-forecasting teams that need booking availability and restaurant profiles rather than item-level delivery pricing. Open time slots and review data are resolved at request time for the date, party size, and city you specify.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.opentable.com/",
"type": "restaurant",
"geo": "us-ny"
}'
// ← response
{
"status": "ok",
"data": {
"name": "...",
"rating": 4.5,
"review_count": 820,
"cuisine": "...",
"delivery_fee": 2.99,
"eta_min": 25,
"menu_items": 142
}
}OpenTable data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Reservation-availability and slot tracking
Restaurant profile and cuisine intelligence
Diner review and rating monitoring
Dining-demand and occupancy forecasting
Yes. Pass a restaurant profile with a date, time, and party size and we return the available reservation slots, the restaurant profile, its menus and price band, and recent diner reviews.
No. OpenTable is a reservations platform, so we return booking availability, restaurant profiles, dining menus, and reviews rather than per-item delivery prices or courier fees.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.