目的地和场所研究
Use TripAdvisor endpoints to turn 目的地和场所研究 into repeatable API requests with documented inputs and JSON responses.
使用规范化的榜单和评论端点，研究 TripAdvisor 上的酒店、餐厅、景点和目的地页面。
采集 TripAdvisor 的自动补全、榜单搜索、地点详情、评论和枚举元数据，用于旅行研究工作流。
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
采集 TripAdvisor 的自动补全、榜单搜索、地点详情、评论和枚举元数据，用于旅行研究工作流。
Use TripAdvisor endpoints to turn 目的地和场所研究 into repeatable API requests with documented inputs and JSON responses.
Use TripAdvisor endpoints to turn 酒店和景点监控 into repeatable API requests with documented inputs and JSON responses.
Use TripAdvisor endpoints to turn 旅行评论分析 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.
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.
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.
MCP tool tripadvisor_hotels
/tripadvisor/placeReturns a rich TripAdvisor place profile.
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.
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.
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 的评论和地点数据受反爬虫防护保护。Crawlora 的 TripAdvisor 端点将搜索、酒店、地点和评论数据返回为结构化 JSON。评论端点接受 TripAdvisor 地点 ID 或规范地点 URL，并提供排序、语言、翻译、评分、分页和照片控制。
使用自动补全或榜单搜索进行发现，打开酒店或地点，或用地点 ID、规范 TripAdvisor URL 二选一调用 /tripadvisor/reviews。
limit 默认 20、上限 50。DEFAULT 或 DATE 选择最新优先，否则保持 TripAdvisor 上游顺序。可重复选择 1–5 星评分、指定语言，并选择翻译文本或原文详情。
获取名称、评分、评论数量、排名、设施，以及包含作者、日期、语言、有帮助数、照片和公开评论 URL 的规范化评论。
定期重新运行以跟踪评分变化、新增评论和竞品场所随时间的变化。
FAQ
将 TripAdvisor 的搜索或地点标识发送给 Crawlora 的 TripAdvisor 端点，即可获得结构化 JSON——名称、评分、评论数量、价位和评论内容——无需应对反爬虫层。请采集公开数据并遵守 TripAdvisor 的条款。
可以。传入 TripAdvisor 地点 ID 或规范地点 URL 二选一。端点会在可用时返回公开评论正文、评分、语言、日期、有帮助数、照片和评论 URL，不会访问私有或登录后的会员数据。limit 上限为 50，评分可重复选择 1–5，关闭机器翻译会请求原文详情。
在遵守 TripAdvisor 使用条款、robots 指令、速率限制和适用法律的前提下，采集公开可访问的地点和评论数据通常是被允许的。这适用于你有权采集的公开数据。