Tripadvisor
Hotels, restaurants and attractions with reviews.
/tripadvisor/v1/reviews1 creditReviews + the full place profile (rating histogram, subratings, amenities) for one or more Tripadvisor places, by page URL.
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| url | optional | — | Tripadvisor page URL of the hotel/restaurant/attraction (the reliable input — copy it from the browser). Provide this OR startUrls. |
| startUrls | optional | — | Several place URLs in one call (strings or {url:…} objects). One minted session is reused across them. |
| query | optional | — | UNRELIABLE: place-name lookup often fails to resolve ('Could not resolve a locationId'). Use `url` instead. |
| queries | optional | — | UNRELIABLE (same lookup as `query`): several place names in one call. Prefer `startUrls`. |
| maxReviews = 200 | optional | 1–10000 | How many of the newest reviews to fetch per place (1–10000). More reviews = longer runtime. |
| language = en | optional | — | Review language filter (ISO 639-1: en, es, de…). Use 'all' for every language (machine-translated). |
/tripadvisor/v1/places/list2 creditsDiscover hotels, restaurants or attractions in a city/area (name, rating, review count) — the feeder for `reviews`.
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| location | required | — | City or area name. Resolved to a Tripadvisor geo automatically (or pin it exactly with geo_id). |
| category = hotels | optional | hotels · restaurants · attractions | What kind of places to list (singular forms also accepted). |
| max_results = 30 | optional | 1–500 | How many places to return (1–500). The engine pages the results internally. |
| geo_id | optional | — | Advanced: Tripadvisor geo ID (the g-number in URLs) — skips the location lookup. |
| location_slug | optional | — | Advanced: the URL slug that pairs with geo_id. |
/tripadvisor/v1/detail2 creditsFull profile for one Tripadvisor hotel, restaurant or attraction by page URL: overall rating, total reviews, ranking, price level, the per-star rating breakdown, category subratings (cleanliness / service / value / location / food / atmosphere), amenities, cuisines, address, coordinates and phone.
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| url | required | — | Tripadvisor page URL of the hotel/restaurant/attraction (copy it from the browser, or get it from `search` / `places/list`). |
/tripadvisor/v1/search1 creditFind Tripadvisor places (hotels, restaurants, attractions) and destinations by name — the typeahead the site's own search box uses. Returns the matching location IDs + page URLs to feed into `reviews` or `detail`.
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| query | required | — | Place or destination name to look up (e.g. 'Bellagio Las Vegas', 'Eiffel Tower', 'Rome'). |
| type | optional | hotel · restaurant · attraction · geo | Optional: keep only one kind of result. |
| limit = 10 | optional | 1–30 | How many candidates to return (1–30). |
curl -X POST https://api.reefapi.com/tripadvisor/v1/reviews \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"startUrls":[{"url":"https://www.tripadvisor.com/Hotel_Review-g45963-d91703-Reviews-Bellagio-Las_Vegas_Nevada.html"}],"maxReviews":45}'{
"ok": true,
"data": { /* the result */ },
"meta": {
"latency_ms": 240,
"record_count": 12,
"completeness_pct": 100
},
"error": null
}Measured at 60 requests a second across the fleet, with no central bottleneck. Volume pricing is on request, and per-key limits are raised for high-volume accounts.
Tell us a site we do not cover yet and it becomes an engine. A customer asked for bestprice.gr on a Sunday and it was in the catalog the next day.
Median time from a question in the live chat to the first answer, measured across every answered conversation. Setup help included, no support tier to buy.
No per-site plans and no separate subscriptions. One key and one credit pool across the whole catalog, so adding a source costs nothing up front.
Planning something large? Tell us the volume and the sources and we will come back with what it costs and what we would have to build.