Tripadvisor Scraper — Hotels, Restaurants & Attractions

Search Tripadvisor and get structured listing rows — name, rating, review count, price range, category, location and the listing URL.

Public marketplace data, assembled for competitive research.

📊 What you get

One record per listing. Fields returned:

Field	Description
name	Listing name
url	Tripadvisor listing URL
category	Hotel / Restaurant / Attraction (or the schema.org type when structured data is available)
rating	Average rating, when published on the results page
reviewCount	Number of reviews, when published on the results page
priceRange	Price band, when published in the listing's structured data
location	Location line from the result card, when present
searchQuery	The query that produced the row

Fields are populated on a best-effort basis from what the results page publishes — rating, reviewCount, priceRange and location come back empty when Tripadvisor does not show them for a given listing. This actor does not return addresses, coordinates, rankings or review text.

▶️ Example input

{
  "searchQuery": "hotels new york",
  "maxResults": 5
}

searchQuery is required. Put the listing type in the query itself ("restaurants paris", "attractions rome").

⏰ Schedule it

Schedule a daily sweep (0 7 * * *) to track listings and ratings over time.

🛡️ Reliability

Tripadvisor uses aggressive anti-bot protection. Every run loads the page through an Apify residential session and retries with a fresh session up to three times. If Tripadvisor serves a bot check instead of results, the run fails with an explanatory message and delivers no rows — you are never charged for a challenge page, and a failed run never lands an error row in your dataset.

💵 Pricing

Pay-per-event:

• $0.020 per listing delivered to the dataset — about 50 listings per $1.
• $0.005 per actor-start GB-event — one-time per run.

You pay for delivered listings only. Blocked runs and no-match runs deliver no rows and charge no result events.

🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it and pull data on demand.

Agentic payments (x402): supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

🔗 Related actors

Travel data family: Airbnb · Booking.com · Travel MCP

---

Public web data, assembled for research and monitoring.