TripAdvisor Restaurant Details Scraper

Yes — a public restaurant page is public data. We read what any diner sees before booking: no login, no private area. How you use it afterwards is on you, so keep outreach relevant. More in our guide to the legality of web scraping.

No login required. No account to sync, no cookie to paste, no Chrome extension to install. Paste your restaurant URLs and go — you don't even need to have eaten there.

32 data points per restaurant. Name, city ranking, overall rating, review count, the 1-to-5 star breakdown, food, service, value and atmosphere scores, awards, cuisines, price range, address, phone, email, website and GPS coordinates.

About 45 restaurants a minute. A 1,000-restaurant city list is done in under half an hour — long before you've picked where to have lunch. Keep URLs from the same TripAdvisor site together and it stays at full speed.

Yes — phone, email and website, each in its own column. Plus the full address and GPS coordinates. When a restaurant hasn't listed an email on TripAdvisor, the cell stays empty: nothing is guessed or made up.

Both, with the year. You get whether the restaurant is in the MICHELIN Guide, its stars, and its Travelers' Choice award type — including Best of the Best. Handy for building a list of the places everyone else is trying to beat.

No — it scrapes the restaurant, not its reviews. You get the review count, the star breakdown and the four sub-ratings, which is the whole reputation at a glance. For every review's text, the TripAdvisor Reviews Scraper does exactly that.

As many as you like — one row per URL. Copy them from TripAdvisor, or pull a whole city with the TripAdvisor Restaurants Search Export and feed its URLs straight in. Any country site works; .com gives the richest ranking details.

Yes — schedule the same list daily, weekly or monthly. Every run records the city ranking, rating and review count again, so you can see who climbed, who slipped and who quietly closed its doors.

Just about anywhere you already work. Google Sheets, Make, n8n, Amazon S3, email, webhooks — plus our MCP server, so Claude or ChatGPT can launch a run and read the results for you. CSV, Excel and JSON downloads too. See all integrations.

URL, such as https://www.tripadvisor.com/Restaurant_Review-g187175-d806529-Reviews-Michel_Sarran-Toulouse_Haute_Garonne_Occitanie.html. Paste thousands at once or upload a CSV; duplicate inputs are skipped. 2 settings shape the run: see them in the playground.

32 data attributes per restaurant, each with its description and an example: see the full list.

No. Duplicates are removed, and you only pay for unique results.

As fresh as your run: each run collects the data from the site at the moment it runs, nothing comes from a stored database.

CSV, Excel or JSON from the dashboard, through the API, or sent after every run to Google Sheets, Amazon S3, an SFTP server, a webhook or by email.

7 days on the free plan, 28 days on paid plans. Then they are deleted. Download or deliver what you want to keep.

Around 45 restaurants a minute for one squid. Your plan's slots run several squids at the same time.

99.80% of its runs had no incident over the last 90 days (1 incident, 100% fixed). Every day is on this page.

Our team fixes the scraper: every scraper on lobstr.io is built and maintained by us. Over the last 90 days, the median time to fix this one was 2h 1min. How we measure.

Yes, on paid plans: every hour, every day, every weekday or on a custom schedule, in your time zone.

Yes: set the most results per task and per run in the settings. The run stops there and so does the bill.

1 credit per result. The playground shows the price as you pick them.

Yes. The free plan gives 100 credits every month, 100 results with this scraper, with exports capped at 30 rows.

Every month a plan gives credits, which pay for results, and slots, which set how many squids run at the same time. Starter: $20 for 10,000 credits; Pro: $100 for 100,000 credits; Team: $500 for 1,000,000 credits. Upgrades start right away and are prorated; downgrades and cancellations take effect at the end of the cycle.

No. Your credits refresh every month with your plan.

You choose, per squid: pause and pick up where it stopped, or end the run. To keep going, upgrade or reset your billing cycle: your plan renews right away and your credits come back. Auto Billing Reset does it for you when your usage crosses a threshold you set.

Yes: paying yearly takes 20% off every plan.

A monthly plan: within 10 days of the charge, if no credit was used in that period. A yearly plan: within 30 days, in full if no credit was used, otherwise minus one month. Cancel from your billing page, then write to contact@lobstr.io. The details are in the terms of use.

Collecting publicly available data is generally allowed, but you choose what you collect and you are responsible for how you use it. Our terms of use (article 6) ask every user to respect the rights of the sites, not to extract substantial parts of a database, not to access confidential data and to follow personal data law such as the GDPR. This is not legal advice.

When results contain personal data, you are the data controller and lobstr.io, a French company, processes them on your behalf, under our personal data agreement. You need a lawful basis for what you collect, must inform the people concerned and honor their requests.

Results: 7 days on the free plan, 28 days on paid plans, then they are deleted; you can delete them sooner. Your account data: see the privacy notice.

It depends on where the people are. In the EU, prospecting businesses by email is generally possible with an opt-out in every message, while consumers must have agreed first; calls follow each country’s do-not-call list. In the US, CAN-SPAM asks for your address and an opt-out in every email. This is not legal advice.

Yes, through the REST API at https://api.lobstr.io/v1, with your key from the dashboard. The playground’s Code tab writes the calls for your settings, in cURL and Python. The documentation has the full reference.

Yes. Add our MCP server, https://mcp.lobstr.io/mcp, to Claude, ChatGPT, Cursor or any MCP client and sign in with lobstr.io. Your agent shows the cost and asks you before a run spends credits. The playground’s Agent tab gives you a prompt.

No. Credits pay for results, not for requests.

Yes. Point a webhook at your server and lobstr.io calls it when a run succeeds or fails.

Yes, per endpoint: 120 requests a minute on squids and runs, 90 on tasks, 2 a second on results. Above that the API answers 429 with a Retry-After header.