TripAdvisor Scraper API — Hotels, Restaurants, Emails, Leads
Pricing
from $2.20 / 1,000 results
TripAdvisor scraper and unofficial TripAdvisor API: hotels, restaurants and attractions with prices, partner offers and booking links, star class, per-category subratings, amenities, cuisines, hours, reservation slots, GPS, phones, emails and full review threads. From $0.25/1k reviews.
Fixed — every place with few reviews silently lost all of them
ReviewsProxy_getReviewListPageForLocation. The premium-proxy health check flagged any short
body containing the word "PROXY" as a dead exit node — so that empty last page read as a
proxy failure, the request was retried on three fresh IPs, and the place's review pull ended
in an error. Every place with fewer reviews than Max reviews per place hit it: the record
was still pushed, with reviews: [], indistinguishable from a place that genuinely has no
reviews. A run of 10 New York places now returns 100 of 100 reviews where it returned 92 and
one hard failure. The gateway check now looks only at bodies that are not a JSON or HTML
document, and a regression test pins the exact response that broke it.reviewsError in the dataset and counted in the run log and
status message — "we could not read them" and "there are none" are no longer the same output.NO_HOST_CONNECTION body rather than an
error, and that was filed as a "blocked request" — the category that gets the most retries by
design, because DataDome blocks a share of IPs normally. It is a refusal, not a block, so it
now drops to the Apify Residential tier underneath almost immediately.Fixed — wasted requests
Added — business emails for restaurants
emails array too. TripAdvisor's restaurant listing exposes
no email and no website field at all (unlike hotels, whose addresses it publishes directly).
The venue's own domain is taken from its TripAdvisor menu link — booking, delivery and social
hosts excluded — and the contact address read from that site, following its contact page (or
trying /contact when the site renders its navigation in JavaScript). Measured over 360
places across 6 cities: 43% of hotels and 37% of restaurants come back with an email,
and 70% of restaurants with a website.website on restaurant records — the venue's own site, which is also where
their emails are read from.reviewsError — present only when the review feed could not be read for that
place. Its absence with reviewsScraped: 0 means the place really has no reviews.Tests
tests/test_transport_guards.py (new, offline) pins all four fixes: the real empty-review-page
body must not read as a gateway error, a short page must not trigger another request, a gateway
refusal must demote the proxy tier at 2, and the email link normalisation.reviewsTail (the
last review page of a place that has 2 reviews — every existing review test used a large hotel
whose page always fills, which is exactly why they stayed green) and emails (hotel addresses
from the listing, restaurant menu links still pointing at their own domain).Added — 33 more fields per place, no extra requests
The GraphQL responses already carried far more than the Actor was mapping. Nothing here costs an extra call; the hotel record went from 34 to 59 fields and the restaurant record from 26 to 39.
subratings: {cleanliness, location, service, value},
the same breakdown TripAdvisor shows on the review tab. Previously only reviews carried subratings.starRating / hotelClass (e.g. 4.0), plus the raw
hotelClassTagId so a class TripAdvisor has not published a mapping for is never dropped.offers now has a bookingUrl that resolves to the
partner's booking page, decoded from TripAdvisor's own commerce token, next to
strikethroughPrice, shortDisplayPrice, pricingMode, priceTrendTier,
availabilityStatus, timeOfPayment, isMemberRate, isMobileRate and providerLogoUrl.reservationOffers carries each partner slot with its
timeslots (dateTime, status, bookingUrl, discountText), plus reservationUrl,
restaurantSpecialOffer, hasMenu and the machine-readable openStatus.isSponsored, isPremium and
merchandisingLabels say when a row is a paid placement instead of an organic result.featuredReview (id, title, text, rating, date, permalink, author and
author profile) and descriptionSource, which says whether description is TripAdvisor's
LLM summary or a real review snippet.businessPhone, businessPhoneRaw and websiteUrl for
Business Advantage listings, alongside the existing emails.rankingDenominator, rankingOutOf, awardYear,
accommodationCategory, parentGeoName, countryId, priceRangeMinUsd, imageCaption,
highlightUrl, notices, establishmentTypeIds, distanceFromCenter and
reviewSnippets (all highlighted excerpts, not just the first).reviewer.username and reviewer.helpfulVotes, plus roomTip,
publishPlatform, originalLanguage, translationType, isMachineTranslated, labels and
createdDate for the locales and place types where TripAdvisor returns them.Docs
Fixed — runs that failed for no good reason
zzzqqq nowhere came back as "The Tunnel To Nowhere", which the Actor scraped and
charged for. A guess that doesn't resemble the query is now reported as "no match" instead.Fixed — language settings that never worked
th) runs failed 100% of the time. The Actor pointed at
www.tripadvisor.com.th, a host that does not exist — every Thai run died on DNS before
reaching TripAdvisor. It now uses the Thai site's real address. All 38 language hosts are
checked by the test suite from now on.Added — pages that used to be refused
/Attraction_Review- URLs and searches like Eiffel Tower now return a
record (name, URL, review count) with their full review threads. Price, amenities and
ranking stay hotel/restaurant-only — TripAdvisor's API doesn't expose them for attractions./Tourism-g... URLs (the page TripAdvisor links to when you click a city)
are scraped as that city's listings./ShowUserReviews-... URLs resolve to the place they belong to./Search?q=Antalya runs that search instead of failing.-d place id resolves through
the review API, a bare -g city id becomes that city's listing. A URL from another site is
now named as such, instead of "unsupported page".Clearer
Fixed
Cannot query field "primaryMedia" — an
HTTP 200 error envelope, which the actor correctly turned into a failed run rather than
an empty dataset. The query has been re-captured from a live session. Restaurants,
search, reviews and place lookups were unaffected.Fixed
errors array, which the actor read as
"no results" — a run could finish green with an empty dataset (this is what made
"Antalya" report "no geographic match" on 2026-08-04). Such responses now raise, and
the run fails with the reason in its status message.d197751 is slugged
"Hotel_Regina_Louvre-Paris" but is actually in Chester) — the POI's real parent geo is
now looked up first, so the search happens in the right city."hotels in Antalya", "Antalya hotels",
"top 10 restaurants in Dubai" used to return nothing at all (TripAdvisor's typeahead
matches place names only). The category is taken from the phrase. Place names containing
a category word ("Hotel Astra Opera Astotel", "Bar Harbor") are left untouched.category: "all" with an item limit now returns a mix: the limit is split evenly between
hotels and restaurants instead of being spent entirely on hotels."Antalya otelleri" (Turkish for
"Antalya hotels") matched no place name and returned nothing; the query is now retried
without its trailing / leading word, which recovers the place name in any language. The
retry only happens after a query came back empty, so a normal search still costs one request.Input — simpler
mode. One search field (cities, regions, geo IDs or place names) plus
startUrls; both are scraped when both are filled. Previously two of the three input
fields were silently ignored, which is how a filled-in form could still scrape nothing.
Inputs that still send mode keep their exact old behaviour and log what is being ignored.maxPois moved to Advanced; maxRetries default lowered from 5 to 3.Less proxy traffic
isPartialRecord: true) instead of being dropped
after ten billed pages.maxRetries + 1 times (each on a fresh IP) instead of up to 75 times, with shorter waits.22 request(s), 0.47 MB ... broken down per endpoint).Faster