[Home](/)[Blog](/blog)TripAdvisor Reviews API: What Replaced the Content API, and How to Get Review Data Now # TripAdvisor Reviews API: What Replaced the Content API, and How to Get Review Data Now ![Denis Gramm, StayAPI](/blog_post_author.png) By Denis Gramm, StayAPI· Jun 25, 2026 ·12 min read I hope you enjoy reading this blog post. If you want our team to help you with hotel data integration, [click here](/book-demo). Quick summary This guide covers TripAdvisor's move from the Content API to Terra, what the official reviews endpoint returns now, and the routes to full review history. ## Table of contents - [Key Takeaways](#key-takeaways) - [Why TripAdvisor Review Data Matters](#why-tripadvisor-review-data-matters) - [Does TripAdvisor Have a Reviews API?](#does-tripadvisor-have-a-reviews-api) - [Four Ways to Access TripAdvisor Review Data](#four-ways-to-access-tripadvisor-review-data) - [What TripAdvisor Review Data Looks Like](#what-tripadvisor-review-data-looks-like) - [Use Cases for TripAdvisor Review Data](#use-cases-for-tripadvisor-review-data) - [Getting Started with StayAPI](#getting-started-with-stayapi) - [FAQ](#faq) ![TripAdvisor Reviews API: What Replaced the Content API, and How to Get Review Data Now | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDAsInB1ciI6ImJsb2JfaWQifX0=--03ad5d3142419930295e31a4ca434b0f7860e393/hero_b.png?disposition=inline) TripAdvisor retired its Content API on August 31, 2026, and the official TripAdvisor reviews API now runs on Terra, its platform for partners. The self-serve Discover package still returns reviews, drawn from a small fixed pool of recent reviews per location. The old 5,000 free calls a month became a one-time allowance of 1,000, with per-location billing after that. For competitor tracking, review history, or cross-OTA dashboards, that pool pushes most teams toward another route. There are four ways to get TripAdvisor review data, and the Terra API is a legitimate one of them. The other three are the management center (manual), extractor tools (fragile), and third-party data providers that return reviews as structured JSON. This guide covers all four, what each returns, and where each one stops scaling. ## Key Takeaways - **TripAdvisor's official reviews API moved to Terra.** The Content API was retired on August 31, 2026, and its keys were deprecated; new access comes from a Terra account. - **The official pool is small by design.** Terra's self-serve Discover package returns a limited number of recent reviews per location, which suits a widget and falls short of monitoring or analysis. - **Four paths exist:** the Management Center (manual), the Terra API (official, small review pool), extractor tools (high-maintenance), and third-party data providers (structured JSON, any public property). - **TripAdvisor review text is richer than most OTAs.** Reviews run longer and more narrative, sub-category bubble ratings are included, and reviewer hometown is usually populated, which is strong input for sentiment and source-market analysis. - **A data API delivers TripAdvisor reviews as structured JSON** alongside [Booking.com](https://stayapi.com/blog/booking-com-reviews-api), [Agoda](https://stayapi.com/blog/how-to-extract-agoda-reviews), [Expedia](https://stayapi.com/blog/expedia-reviews-api), [Airbnb](https://stayapi.com/blog/how-to-access-airbnb-review-data), and Google Hotels through one integration. ## Why TripAdvisor Review Data Matters ![Why TripAdvisor Review Data Matters | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDIsInB1ciI6ImJsb2JfaWQifX0=--7df87bfa4b39b24ae63645c1e33275c0dd38bb02/why_tripadvisor_review_data_matters_b.png?disposition=inline) A hotel's TripAdvisor rating still shapes the decision even when the guest books somewhere else. The text itself is unusually good. TripAdvisor reviews run longer and more narrative than Booking.com or Agoda reviews, which makes them richer input for sentiment analysis and qualitative research. A guest writing three paragraphs about their stay gives you far more signal than a one-line rating. There's also the awards angle. TripAdvisor's Travelers' Choice recognition carries real marketing weight, and it's driven by review recency, volume, and rating consistency. **If you want to model your trajectory toward (or away from) that recognition, you need the underlying review data, tracked over time.** Every TripAdvisor property has a unique location ID, the numeric identifier in its URL. That ID is the key to every TripAdvisor data workflow, and we'll come back to it in the getting-started section. ## Does TripAdvisor Have a Reviews API? ![Does TripAdvisor Have a Reviews API? | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDMsInB1ciI6ImJsb2JfaWQifX0=--0717962224eb9f1405054c55b7b7aba307c7c316/does_tripadvisor_have_a_reviews_api_a.png?disposition=inline) Yes, and it now lives on Terra. TripAdvisor retired the Content API on August 31, 2026, and deprecated its keys ([Terra migration FAQ](https://docs.terra.tripadvisor.com/docs/faq)). Terra is TripAdvisor's content platform for partners, and its self-serve Discover package includes a reviews endpoint addressed by location ID. Access is pay-as-you-go: the first 1,000 billable entities are free once per account, and each TripAdvisor review API call after that bills one entity per location. Our [TripAdvisor API pricing guide](https://stayapi.com/blog/tripadvisor-api-pricing) works through the per-entity math. The constraint that rules it out for a lot of teams is depth: **the [Location Reviews endpoint](https://docs.terra.tripadvisor.com/reference/locationreviewsget) draws from a fixed pool of recent reviews set by your package.** Discover gets a limited number of reviews per location, and filters narrow that pool without widening it. That's enough to show fresh reviews on a page, and far short of a hotel's review history for trend or sentiment work. Discover also caps usage at 10 requests per second and 10,000 calls a day, and display rules come attached: TripAdvisor branding and attribution on reviews and ratings. It's the right tool for showing a few fresh TripAdvisor reviews on a hotel or travel site. For portfolio monitoring, review history, sentiment analysis, or multi-OTA consolidation, a third-party provider is the more practical path. ### What Changed When the Content API Shut Down | | **Content API (retired August 31, 2026)** | **Terra Discover** | | --- | --- | --- | | **Reviews per location** | Up to 5 most recent | A limited, fixed pool of recent reviews set by the package | | **Free usage** | 5,000 calls a month | 1,000 billable entities, once per account | | **Paid usage** | Pay-as-you-go per call | Per billable entity, $0.015 falling to $0.009 at volume | | **Keys** | Deprecated | New account and key from tripadvisor.com/developers | A TripAdvisor Content API integration needs a new Terra account and key, because old accounts and keys don't carry over. ## Four Ways to Access TripAdvisor Review Data ![Four Ways to Access TripAdvisor Review Data | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDUsInB1ciI6ImJsb2JfaWQifX0=--6794b53e42e676694f3c6ed4a9497401513972cf/four_ways_to_access_tripadvisor_review_data_a.png?disposition=inline) ### Option 1: TripAdvisor Management Center (Manual) Property owners and managers can view and respond to reviews in the TripAdvisor Management Center. Everything is visible in the UI. No bulk export, no structured data, no programmatic access. Good for an owner responding to reviews by hand. It doesn't scale past one property, and it gives you nothing your software can read. ### Option 2: TripAdvisor Terra API (Official, Small Review Pool) Sign up for a Terra account and the Discover package, and you get the reviews endpoint, addressed by location ID. Good for a site or app that shows a handful of current TripAdvisor reviews next to a listing. The limits are real: a fixed pool of recent reviews per location, display and attribution rules, pay-as-you-go billing after the free allowance, and no multi-OTA consolidation. For its intended use (fresh reviews on a consumer-facing page) it works well. ### Option 3: Extractor Tools Marketplace scrapers and custom Python extractors pull reviews straight from property pages, including the full history the official pool leaves out. TripAdvisor runs active bot detection, so they need ongoing maintenance and break when the page structure shifts. Our [TripAdvisor scraper guide](https://stayapi.com/blog/tripadvisor-scraper) covers the method and its real costs. ### Option 4: A Property Data API Third-party data providers run a maintained API that returns TripAdvisor reviews as structured JSON, with a hotel's full review history paged 20 at a time. StayAPI's [TripAdvisor API](https://stayapi.com/apis/tripadvisor) is one example. It covers any public TripAdvisor property, your own and your competitors', and returns the same schema as Booking.com, Agoda, Expedia, Airbnb, and Google Hotels. Good for portfolio-scale monitoring, competitive intelligence, and multi-OTA review consolidation. ### How the Four Options Compare | | **Management Center** | **Terra API** | **Extractor Tools** | **Data API (StayAPI)** | | --- | --- | --- | --- | --- | | **Reliability** | High | High (official) | Medium | High | | **Update frequency** | Manual | On-demand, fixed recent-review pool | On-demand | Real-time, on request | | **Competitor data** | No | Yes, within the pool | Yes | Yes | | **Multi-OTA support** | No | No | No | Yes (Booking.com, Agoda, Expedia, Airbnb, Google Hotels, and more) | | **Access barrier** | Login only | Self-serve account, pay-as-you-go after 1,000 free | None | API key signup | | **Production-ready** | No | Limited | No | Yes | ## What TripAdvisor Review Data Looks Like ![What TripAdvisor Review Data Looks Like | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDcsInB1ciI6ImJsb2JfaWQifX0=--91c044ed89ef9fd2e87ca00e965a9319338fa300/what_tripadvisor_review_data_looks_like_a.png?disposition=inline) TripAdvisor's schema is one of the richer ones, and the review text is the standout. ### Fields Available | Field | Example Value | Description | | --- | --- | --- | | **Review text** | "Having spent more than four months at Allamanda..." | Full guest comment, typically longer than other OTAs | | **Overall rating** | `5` | TripAdvisor's 1-5 bubble scale | | **Sub-ratings** | `{ "value": 5, "rooms": 5, "location": 5, "service": 5 }` | Per-category bubble ratings, where the guest left them | | **Trip type** | `"FAMILY"` | SOLO, COUPLES, FAMILY, BUSINESS, FRIENDS | | **Reviewer hometown** | `"United States"` | Reviewer's home city and country, when given | | **Review date** | `"2026-07-22"` | When the review was published | | **Owner response** | `{ "text": "Dear Richard, Thank you...", "published_date": "2026-10-15", "author": "Strand Palace" }` | The property's reply when there is one (from a London hotel; the example resort doesn't reply, so it's `null`) | | **Review URL** | `"https://www.tripadvisor.com/ShowUserReviews-g1224250-d305165-r1069599874-..."` | Link back to the review on TripAdvisor | A few things stand out compared to other OTAs. TripAdvisor reviews average noticeably longer than Booking.com reviews, so there's more text per review for NLP to work with. Reviewer hometown was filled on 15 of the 20 newest reviews for the example property below, enough to segment feedback by source market without extra enrichment. Sub-category bubble ratings (cleanliness, service, value, location, rooms, sleep quality) come through when the guest provided them, which was 10 of those 20. One normalization note: TripAdvisor's 1-5 bubble scale differs from Booking.com's 10-point and Expedia's 10-point-with-label scales. If you're consolidating across OTAs, you'll want to bring them onto a common scale (a good data API returns each platform's native scale cleanly so you can map them). ### Sample API Response Here's what the review data looks like from StayAPI's TripAdvisor reviews endpoint: ``` { "success": true, "location_id": 305165, "total_count": 359, "reviews": [ { "id": 1069599874, "rating": 5, "title": "A Quiet and Peaceful Retreat Wrapped in Beautiful Gardens", "text": "Having spent more than four months at Allamanda, I can offer a comprehensive perspective on this property...", "language": "en", "published_date": "2026-07-22", "user": { "hometown": "United States" }, "trip_info": { "stay_date": "2025-09-01", "trip_type": "FAMILY" }, "additional_ratings": { "value": 5, "rooms": 5, "location": 5, "service": 5, "sleep quality": 5 } } ], "pagination": { "page": 1, "per_page": 20, "total_pages": 18, "has_next": true } } ``` That's the newest of 20 reviews returned for a Phuket resort (location 305165), pulled on October 15, 2026. ## Use Cases for TripAdvisor Review Data ![Use Cases for TripAdvisor Review Data | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDksInB1ciI6ImJsb2JfaWQifX0=--90a60bfa39d99f24d02eb13148ede46e81328ff7/use_cases_for_tripadvisor_review_data_a.png?disposition=inline) TripAdvisor's strengths (long text, hometown data, brand authority) shape what it's best for. - **Brand reputation monitoring.** TripAdvisor ratings influence bookings even when guests book elsewhere. Pulling reviews on a schedule catches a slide before it compounds into lost search visibility. - **Qualitative research and NLP.** The longer, more narrative text is richer input for [sentiment analysis](https://stayapi.com/blog/hotel-review-sentiment-analysis), topic modeling, and complaint categorization than shorter OTA reviews. - **Source market segmentation.** Reviewer hometown is filled on most reviews. Split feedback by traveler origin with no extra enrichment step. - **Travelers' Choice tracking.** The ranking weights recency, volume, and rating consistency. Tracking review data over time lets you model your trajectory and act before an award window closes. - **Competitive intelligence.** Pull full review history for comp-set properties, beyond the recent-review pool Terra returns. For independent and boutique hotels, TripAdvisor is often the most review-rich source there is. - **Cross-OTA consolidation.** Combine TripAdvisor's narrative text with Booking.com's pre-labeled sentiment and Agoda's nationality data in one schema. ## Getting Started with StayAPI ![Getting Started with StayAPI | StayAPI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NTEsInB1ciI6ImJsb2JfaWQifX0=--07be2fe4d85f204a0fffc2dbca3d812ee09b3093/getting_started_with_stayapi_a.png?disposition=inline) 1. Sign up at [stayapi.com](https://stayapi.com/users/sign_up). No credit card and no Tripadvisor account needed. 2. Try the [free TripAdvisor reviews tool](https://stayapi.com/free-tools/tripadvisor-reviews) to preview the data before writing any code. Paste a property URL and see the structured response. 3. Find your location ID. It's the number after `d` in any TripAdvisor property URL, for example `.../Hotel_Review-g1224250-d305165-...` → `305165`. You can pass either the location ID or the full URL (the [TripAdvisor location ID guide](https://stayapi.com/blog/tripadvisor-location-id) covers every place to find it). 4. Make your first call: ``` curl -X GET "https://api.stayapi.com/v1/tripadvisor/hotel/reviews/305165?page=1&per_page=20" \ -H "x-api-key: YOUR_API_KEY" ``` You provide the location ID and your API key → you get structured JSON back with the review text, bubble rating, sub-ratings, trip type, and reviewer hometown. For the full endpoint reference, see the [TripAdvisor reviews API documentation](https://stayapi.com/docs/endpoints/tripadvisor/hotel-reviews). Pipe it into your own system, Google Sheets, [Looker Studio](https://stayapi.com/integrations/tripadvisor-reviews-to-looker-studio), Power BI, or no-code tools like N8N and Make.com. For teams wanting a walkthrough, [book a demo call](https://stayapi.com/book-demo). ## FAQ ### Does TripAdvisor have a reviews API? Yes, through Terra. The self-serve Discover package returns a small fixed pool of recent reviews per location, for any location your package can access. The Content API that used to serve reviews was retired on August 31, 2026. ### Can I still get a TripAdvisor Content API key? Content API keys were deprecated on August 31, 2026, and old accounts don't carry over to Terra. New keys come from a Terra account at tripadvisor.com/developers, starting with the self-serve Discover package. ### What is the TripAdvisor Terra API? Terra is TripAdvisor's content platform for partners and the replacement for the Content API. It serves location details, reviews, photos, and destination data in tiered packages, from the self-serve Discover package up to contracted tiers with higher limits and wider access. ### Can I get TripAdvisor reviews for competitor properties? Yes, within Terra's recent-review pool. For a competitor's full review history, a third-party provider like StayAPI covers any public TripAdvisor listing. ### What is a TripAdvisor location ID and how do I find it? It's the unique numeric identifier TripAdvisor assigns each property. You'll find it in the property URL as the number after `d`, for example `d305165`. StayAPI accepts either the location ID or the full TripAdvisor URL. ### How often does TripAdvisor review data update via StayAPI? It's real-time. You make a call, you get current data back, with no batch sync to wait on. ### How do TripAdvisor reviews compare to Booking.com reviews? TripAdvisor reviews are typically longer and more narrative, with sub-category bubble ratings and reviewer hometown. Booking.com splits reviews into separate positive and negative fields with sub-scores, more structured but shorter. Both are valuable, for different kinds of analysis. Ship in 3 days ## Ready to simplify your hotel data? Join other developers using StayAPI to build the next generation of travel applications. Get started for free today. [Start Building Free](/users/sign_up)[Book a Demo](/book-demo) [← Back to Blog](/blog)[Previous: Expedia Reviews API: How to Access and Use Expedia Guest Review Data →](/blog/expedia-reviews-api) Hotel data ### Want accurate hotel data? Stop building data pipelines and start building product. Reliable access to hotel reviews, prices, and details with StayAPI. [Book a Demo](/book-demo) ## Table of contents - [Key Takeaways](#key-takeaways) - [Why TripAdvisor Review Data Matters](#why-tripadvisor-review-data-matters) - [Does TripAdvisor Have a Reviews API?](#does-tripadvisor-have-a-reviews-api) - [Four Ways to Access TripAdvisor Review Data](#four-ways-to-access-tripadvisor-review-data) - [What TripAdvisor Review Data Looks Like](#what-tripadvisor-review-data-looks-like) - [Use Cases for TripAdvisor Review Data](#use-cases-for-tripadvisor-review-data) - [Getting Started with StayAPI](#getting-started-with-stayapi) - [FAQ](#faq) About StayAPI StayAPI: Hotel Data API For travel-tech developers We collect, clean, and standardize hotel data so you can build amazing travel products without maintaining your own data collection. 50+ Endpoints 5 Major Platforms Supported sources Booking.comTripAdvisorAirbnbAgodaGoogle Hotelsand more