Search OpenTable and Resy in one Apify Actor, then export restaurant names, ratings, prices, photos, source URLs, and reservation context. Useful for lead lists, market research, local SEO, and restaurant data workflows.
No reviews yetBe the first to leave a review for OpenTable + Resy Scraper
Maker
📌
Hi Product Hunt,
I just launched OpenTable + Resy Scraper on Apify.
It searches OpenTable, Resy, or both in one run and saves restaurant rows to a dataset. You can search by city, cuisine, or keyword, or paste direct venue URLs and slugs.
It exports fields like names, ratings, prices, review counts, neighborhoods, photos, source URLs, and Resy availability for direct venue runs.
It is built for people doing restaurant lead lists, local market research, local SEO, or data workflows that need clean restaurant data without opening every page by hand.
If you try it, please let me know what you think 🫡
Report
How does it handle rate limits or blocks from OpenTable and Resy when scraping at scale, and is the pricing based on results or compute time?
Report
How does it handle the reservation availability data since both platforms typically require interaction to see real-time slots?
Report
Finally one scraper that pulls from both OpenTable and Resy at the same time, saved me a bunch of time building lead lists for a restaurant client. Pricing data on each result was a nice touch too.
Report
How does this handle rate limits or blocks from OpenTable and Resy when running large scrapes? Curious if it’s something I can safely schedule to run daily without worrying about getting IP-banned.
Report
the merge of both platforms into a single Actor is genuinely useful, saves the headache of juggling two separate scrapers. love that it pulls photos and source URLs alongside the ratings, makes the export actually ready for a real workflow.
Report
Finally got around to checking this out and the dual-source approach actually saves a ton of time compared to scraping them separately. Exported a sample of NYC spots with ratings and reservation URLs in one run, very clean output.
How does it handle rate limits or blocks from OpenTable and Resy when scraping at scale, and is the pricing based on results or compute time?
How does it handle the reservation availability data since both platforms typically require interaction to see real-time slots?
Finally one scraper that pulls from both OpenTable and Resy at the same time, saved me a bunch of time building lead lists for a restaurant client. Pricing data on each result was a nice touch too.
How does this handle rate limits or blocks from OpenTable and Resy when running large scrapes? Curious if it’s something I can safely schedule to run daily without worrying about getting IP-banned.
the merge of both platforms into a single Actor is genuinely useful, saves the headache of juggling two separate scrapers. love that it pulls photos and source URLs alongside the ratings, makes the export actually ready for a real workflow.
Finally got around to checking this out and the dual-source approach actually saves a ton of time compared to scraping them separately. Exported a sample of NYC spots with ratings and reservation URLs in one run, very clean output.