Destination and venue research
Use TripAdvisor endpoints to turn destination and venue research into repeatable API requests with documented inputs and JSON responses.
Research hotels, restaurants, attractions, and destination pages from TripAdvisor with normalized listing and review endpoints.
Collect TripAdvisor autocomplete, listing search, place details, reviews, and enum metadata for travel research workflows.
Endpoint families
6
Documented params
59
Examples
6
Live catalog snapshot
Active endpoints
6
Methods
GET
Required params
10
Schema refs
6
{
"platform": "TripAdvisor",
"endpoint": "tripadvisor-autocomplete",
"method": "GET",
"path": "/tripadvisor/autocomplete",
"auth": "apiKey"
}Related use cases
Use cases
Collect TripAdvisor autocomplete, listing search, place details, reviews, and enum metadata for travel research workflows.
Use TripAdvisor endpoints to turn destination and venue research into repeatable API requests with documented inputs and JSON responses.
Use TripAdvisor endpoints to turn hotel and attraction monitoring into repeatable API requests with documented inputs and JSON responses.
Use TripAdvisor endpoints to turn travel review analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live TripAdvisor endpoint catalog — 6 endpoints, 59 documented request parameters, and 6 published response schemas — the same catalog Docs and Playground run against.
6 documented TripAdvisor endpoints, grouped into 6 request families — Autocomplete, Enums and Hotels, plus 3 more.
59 request parameters are documented across those TripAdvisor endpoints, 10 of them required — the full input contract is public before you write any integration code.
6 of the 6 TripAdvisor endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
TripAdvisor endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
6 hosted MCP tools back the TripAdvisor endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/tripadvisor/autocomplete
/tripadvisor/enums
/tripadvisor/hotels
/tripadvisor/place
/tripadvisor/reviews
/tripadvisor/search
Endpoint catalog
/tripadvisor/autocompleteReturns TripAdvisor typeahead suggestions for the required query `q`, optionally narrowed by `limit`, `locale`, `scope_geo_id` and a `type` hint. Each result has its id, title, type, URL, image, parent location and coordinates, and may carry nested search shortcuts. Results can be locations, hotels, restaurants or attractions.
Sampled 14 Oct 2026: 4 items, 3 fields filled in every item, 7 not. title: “California” and 3 other values; url: tripadvisor.com.
MCP tool tripadvisor_autocomplete
/tripadvisor/enumsReturns the values TripAdvisor place and listing filters accept: `locales`, `currencies`, `languages`, `listing_types`, `sorts`, `pricing_modes`, `hotel_classes`, `hotel_amenities`, `restaurant_types`, `restaurant_options`, attraction categories with their ids, and `filter_ids`. It also lists `unsupported_entity_types`. Takes no parameters.
Sampled 14 Oct 2026: 24 of 24 fields returned with a value. locales: 17 entries; currencies: 23 entries.
MCP tool tripadvisor_enums
/tripadvisor/hotelsSearches TripAdvisor hotels in the area given by the required `geo_id`. Filter with `class`, `amenities`, `price_min`, `price_max`, `pricing_mode`, `travelers_choice` and `currency`; page with `offset` and `limit`; order with `sort`. Each hotel has its title, URL, image, rating, review count, star rating, rank, price, provider, location and a review snippet when TripAdvisor supplies them.
Sampled 14 Oct 2026: 3 items, 18 fields filled in every item, 3 not. rating: 3.1 to 4.5, median 4.4; title: “Rambler Oasis Hotel” and 2 other values.
MCP tool tripadvisor_hotels
/tripadvisor/placeReturns a rich TripAdvisor place profile.
Sampled 14 Oct 2026: 14 items, 2 fields filled in every item, 1 not. type: booking (10), website (2), canonical (1) and 1 more; url: en.tripadvisor.com.hk and 2 other hosts.
MCP tool tripadvisor_place
/tripadvisor/reviewsReturns reviews for a TripAdvisor place identified by `id` (location id) or `url`. `limit` defaults to 20 (max 50); `page` is 1-based; `language`, `ratings` (1 to 5) and `sort_by` refine the list. Each review has author, title, text, dates, rating, language, helpful votes, photos and URL. A page beyond `total` returns an empty `reviews` array.
Response notes
Query parameters: pass either `id` with a TripAdvisor location id or `url` with a TripAdvisor place URL. Optional parameters include `page`, `limit`, `language`, `sort_type`, `sort_by`, repeated `ratings`, `do_machine_translation`, and `photos_per_review_limit`. `sort_type` accepts `ML_SORTED` (default) and `DEFAULT`. `sort_by` accepts `FAVORABLE_RATING` (default) and `DATE`. These legacy labels are compatibility inputs for the current frontend: `DEFAULT` or `DATE` selects newest first; otherwise Tripadvisor determines the order. `FAVORABLE_RATING` no longer guarantees an ordering by highest rating. `ratings` accepts repeated values `1`, `2`, `3`, `4`, and `5`. `limit` defaults to 20 and is capped at 50. Requests above 20 combine bounded upstream pages and detail batches while preserving the requested page offset and order. `photos_per_review_limit` defaults to 7 and is capped at 20. `do_machine_translation` defaults to true: title/text use the list’s requested-language version. When false, the detail query returns original-language text. The language filter selects reviews available in the requested language, including translations; photos are capped after normalization. Pagination preserves the upstream list order, and `total` is the count after filters. A verified empty list or a page beyond `total` returns an empty `reviews` array. Missing list/detail data, query retirement, and blocked requests return an upstream error. Returns TripAdvisor public reviews. Review records include author, title, text, dates, rating, language, helpful votes, photos, and public review URLs when available.
Sampled 14 Oct 2026: 3 items, 15 fields filled in every item, 1 not. date: 2026-08-08 to 2026-08-30; url: tripadvisor.com.
MCP tool tripadvisor_reviews
/tripadvisor/searchSearches TripAdvisor places in the area given by the required `geo_id`, for the required `type`: `hotel`, `restaurant`, `attraction`, `all`, or an attraction category type from `/tripadvisor/enums`. Hotel and restaurant filters, `offset`, `limit`, `locale`, `currency` and `sort` are optional. Each result has title, URL, rating, review count, rank, price and location. Unsupported entity-only types return a validation error.
Sampled 14 Oct 2026: 3 items, 10 fields filled in every item, 1 not. rating: 4.6 to 4.9, median 4.9; title: “Kushiro” and 2 other values.
MCP tool tripadvisor_search
Related APIs
Travel & Hospitality
Build travel and lodging research workflows from structured Airbnb stay, room, availability, and review data.
Travel & Hospitality
Turn Expedia's Stays, Flights, and Things To Do results into structured JSON — destination search, hotel listings with pricing and reviews, flight offers, and activity search, sourced from the same API the official mobile app uses. Credential-free.
Travel & Hospitality
Turn Booking.com's hotel, flight, and attractions surfaces into structured JSON — search results, hotel detail with rooms and photos, guest reviews, flight offers, and things-to-do listings, replayed directly against Booking.com's own persisted-query GraphQL and REST endpoints. Credential-free.
Company coverage
TripAdvisor, Inc. · TRIP
TripAdvisor is operated by TripAdvisor, Inc. (TRIP). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the TripAdvisor endpoints above.
SEC filings & financials API →How to scrape TripAdvisor
TripAdvisor's reviews and place data sit behind anti-bot defenses. Crawlora's TripAdvisor endpoints return search, hotel, place, and review data as structured JSON. The reviews endpoint accepts either a TripAdvisor location id or a canonical place URL and exposes the current sort, language, translation, rating, pagination, and photo controls.
Use autocomplete or listing search for discovery, open one hotel or place, or call /tripadvisor/reviews with either its location id or canonical TripAdvisor URL.
For reviews, limit defaults to 20 and is capped at 50. DEFAULT or DATE selects newest first; otherwise TripAdvisor keeps its upstream order. Filter repeated ratings from 1 to 5, select a language, and choose whether detail text uses the translated or original-language version.
Receive names, ratings, review counts, rankings, amenities, and normalized reviews with author, dates, language, helpful count, photos, and public review URLs when available.
Re-run to track rating changes, new reviews, and competitor venues over time.
FAQ
Send a TripAdvisor search or place reference to Crawlora's TripAdvisor endpoint and get structured JSON — name, rating, review count, price level, and reviews — without fighting the anti-bot layer. Collect public data and respect TripAdvisor's terms.
Yes. Pass either a TripAdvisor location id or a canonical place URL. The endpoint returns publicly visible review text, rating, language, dates, helpful count, photos, and review URL when available; it does not access private or logged-in member data. limit is capped at 50, ratings can be repeated from 1 through 5, and disabling machine translation requests original-language detail text.
Collecting publicly accessible place and review data is generally permissible if you respect TripAdvisor's terms of use, robots directives, rate limits, and applicable law. This is for public data you're authorized to collect.