Tripadvisor Data Scraper avatar

Tripadvisor Data Scraper

Under maintenance

Pricing

Pay per usage

Go to Apify Store
Tripadvisor Data Scraper

Tripadvisor Data Scraper

Under maintenance

Fetch public Tripadvisor place metadata by detail URL or location ID. Wraps the Tripadvisor Data Scraper API as an Apify Actor that writes normalized place profile, rating, ranking, amenity, award, and photo metadata to the default dataset.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

4 days ago

Last modified

Share

What this Actor does

Fetch public Tripadvisor place metadata by detail URL or location ID. Wraps the Tripadvisor Data Scraper API as an Apify Actor that writes normalized place profile, rating, ranking, amenity, award, and photo metadata to the default dataset.

Input example

{
"placeUrls": [
"example-placeUrl"
]
}

Input fields

Provide Tripadvisor place URLs or numeric location IDs to fetch. Each input becomes one dataset item.

  • placeUrls (array, user input): Public Tripadvisor detail URLs for hotels, restaurants, attractions, or rentals.
  • locationIds (array, user input): Numeric Tripadvisor location IDs. A full place URL is more reliable when available.
  • apiBaseUrl (string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.

Output dataset

Each dataset item is one normalized Tripadvisor place response.

  • input: Original Tripadvisor URL or location ID.
  • locationId: Tripadvisor numeric location ID.
  • name: Place name.
  • type: hotel, restaurant, attraction, rental, or unknown.
  • rating: Aggregate Tripadvisor rating.
  • reviewCount: Aggregate review count.
  • address: Public place address.
  • result: Full upstream API response.

Developer notes

Set TRIPADVISOR_DATA_SCRAPER_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push