TripAdvisor API

The TripAdvisor API for reviews, ratings, and prices.

Pull guest reviews, ratings, multi-provider prices, search results, and property details from TripAdvisor as clean JSON.

REQUEST GET
USE CASE Search TripAdvisor hotels in a destination by geo_id across dates.
curl "https://api.stayapi.com/v1/tripadvisor/search" \
  -G \
  -H "x-api-key: $STAYAPI_KEY" \
  -d "geo_id=293916" \
  -d "check_in=2026-06-18" \
  -d "check_out=2026-06-20" \
  -d "adults=2" \
  -d "rooms=1" \
  -d "limit=10" \
  -d "sort=BEST_VALUE"
RESPONSE 200 OK
2.41s
{
  "success": true,
  "geo_id": 293916,
  "hotels": [
    {
      "location_id": 8950960,
      "name": "Hotel Clover Asoke",
      "rating": 4.5,
      "review_count": 2345,
      "price": {
        "minimum": 85,
        "maximum": 210
      },
      "property_type": "HOTEL",
      "neighborhood": "Asoke",
      "merchandising_labels": [
        "Travellers' Choice"
      ]
    }
  ]
}
99.9% uptime ~3s avg response Live, not cached

Trusted by hospitality teams at

Overview

What the TripAdvisor API gives you.

TripAdvisor has no open data API for the reviews, ratings, and competing rates that revenue and product teams actually need. The usual answer is a scraping stack: headless browsers, rotating proxies, GraphQL replays, and a parser that breaks every time the page changes.

StayAPI is that layer, run for you. You send a location_id or a TripAdvisor URL and get structured JSON back: review text and bubble ratings, prices from Priceline, Booking.com, Agoda and other providers side by side, search results by destination, and the full property profile. The same data, the same shape, on every call.

01

One key, every endpoint.

x-api-key in, JSON out. Reviews, ratings, prices, search, and details behind one base URL. No SDK to install.

02

We run the hard part.

Fetching, parsing, GraphQL handling, and proxy rotation are ours. You consume normalized JSON and never touch a headless browser.

03

Real-time, not cached.

Every call hits TripAdvisor live, so ratings, review counts, and provider prices are current to the request, not a stale nightly snapshot.

Use cases

What teams build on the TripAdvisor API.

The same endpoints, pointed at different jobs. These are the ones we see most.

01

Review monitoring.

Stream new TripAdvisor reviews into your dashboard, ordered most-recent-first, and run sentiment or topic clustering on the text and trip types.

02

Rating benchmarking.

Track a property's bubble rating and review count over time, and benchmark them against the comp set using the same fields for every hotel.

03

Rate shopping and parity.

Pull TripAdvisor's multi-provider prices per date and compare Priceline, Booking.com, Agoda and others against your own rate to catch parity slips.

04

Hotel search and metasearch.

Power a search experience with live TripAdvisor inventory by destination, dates, price range, and rating, sorted by best value or traveler ranking.

05

Market and compset analysis.

Resolve a destination to its geo_id, pull every hotel in it, and score rank, rating, and price across the whole market in one pass.

06

AI travel agents.

Feed structured TripAdvisor reviews and provider prices into an LLM tool call so your agent answers from live data, not stale embeddings.

Pricing

100 free requests on signup.
Pick a plan when you need more.

Flat monthly plans, every endpoint included on every plan. 1 request = 1 credit. No per-endpoint multipliers, no surprise overages.

01 Free

Wire it up. See the schema.

$0 to start
  • 100 free requests on signup
  • Every endpoint included
  • No credit card required
  • Same schema as paid
Start free
02 Basic

Kick the tires in production.

$49 per month
  • 1,500 requests / month
  • Every endpoint included
  • Per-endpoint usage dashboard
  • Email support
Start Basic
04 Scale

Daily pulls in production.

$450 per month
  • 100,000 requests / month
  • Every endpoint included
  • Per-endpoint usage dashboard
  • Priority email support
Start scaling
05 Custom

Above 100k / month, annual terms, white-glove onboarding.

Let's talk
  • 1M+ requests / month
  • Volume rate on the call
  • Per-endpoint usage dashboard
  • Priority email + Slack support
Book a scoping call

Every plan ships every endpoint. Same uptime, same schema, same response time.

Questions

What people ask about the TripAdvisor API.

Don't see your question? Email us at info@stayapi.com.

Does TripAdvisor have a public API?

TripAdvisor runs a Content API for licensed partners, but it is gated, contract-bound, and not built for pulling full review text, ratings history, or competing provider rates. StayAPI gives you that data over plain REST with a key you get in 30 seconds.

How do I get TripAdvisor reviews?

Call /v1/tripadvisor/hotel/reviews/{location_id} (or resolve the ID from a URL with location/extract-id). You get paginated review text, ratings, trip type, reviewer profile, and stay dates as JSON, most recent first. See the reviews endpoint docs.

Can I get TripAdvisor ratings via API?

Yes. Search and details return the property's bubble rating and review_count, and each review carries its own rating plus category scores for value, service, and cleanliness. Track them per call to benchmark a hotel against its comp set.

What is a location_id?

It is the numeric ID TripAdvisor uses for a hotel, the number after d in a hotel URL (for example 305165 in /Hotel_Review-g1224250-d305165-...). Pass it to details, prices, and reviews. Don't have one? Use location/extract-id or the -from-url endpoints to skip the lookup.

Is the TripAdvisor API free?

You get 100 free requests on signup, every endpoint included, no credit card. After that it is flat monthly plans starting at $49. One request equals one credit, with no per-endpoint multipliers.

Two ways to start.

Both end with live TripAdvisor data in your stack. The fast path is on the left.

01 · the fast path

Try it free

100 free requests after sign up. Fastest way to see if the schema fits.

Start free
  • Live API key in 30 seconds
  • No credit card required
  • Same schema as paid
02 · the scoped path

Book a scoping call

15 minutes. Volume + endpoint mix. Walk out with a quote.

Book a demo
  • Quote on the call, not after
  • Engineering, not sales
  • No deck, no slides