Booking.com, Expedia and Tripadvisor Reviews by API: What's Possible

Guest reviews in hospitality are spread across the sites where people booked: Booking.com, Expedia, Hotels.com, Agoda, Airbnb, Tripadvisor and Google. Hotel tech products usually need all of them. Here is what each of the big three offers officially, and where it stops.

Booking.com: partner access only

Booking.com has two APIs that touch reviews, and neither is open.

• The Demand API has an /accommodations/reviews endpoint, but only "if your partner agreement with Booking.com allows it". You need to be a Managed Affiliate Partner. (Booking.com Demand API)
• The Guest Review API on the connectivity side reads reviews and posts replies, but it's "for internal use by properties". Its docs also say reviews retrieved through it "may not be used on your public page". (Guest Review API)

If you aren't a Booking.com partner or the property itself, there's no official route.

Expedia: through your account manager

Expedia's Rapid API has a Guest Reviews endpoint that returns "up to 100 reviews" per property. They can be cached for up to 48 hours, and access is arranged "through your Expedia representative". (Rapid Guest Reviews) It's built for booking partners showing reviews at the point of sale, not for review analytics.

Tripadvisor: the Content API is gone

For years the answer was the Tripadvisor Content API, which "returns up to 5 of the most recent reviews" per location. It's been deprecated, with keys set to stop working on 31 August 2026. (Content API, migration FAQ)

Its replacement, Terra, works differently:

• the reviews you can read come from a contract-defined pool, such as "the N most recent reviews or every review published in the last M months";
• pricing is per entity, with the first 1,000 free, then $0.015 each and less at volume;
• caching "is not permitted for any content" except the location ID.

(Terra reviews, pricing, caching policy)

The no-caching rule is the one that hurts analytics products. Terra fits live display, not storing reviews to analyse later.

What this means in practice

	Who can use it	Full text	History you can keep
Booking.com	Partners and properties	Yes	Restricted
Expedia Rapid	Booking partners	Yes, up to 100	48 hours
Tripadvisor Terra	Contracted customers	Contract-defined	No caching

A hotel reputation or guest-experience platform usually wants the opposite of all three: every review, from every site, stored with its history, for properties that may not have connected anything yet.

How ReviewLake fits

ReviewLake collects publicly visible guest reviews from Booking.com, Expedia, Hotels.com, Agoda, Airbnb, Trip.com, HolidayCheck, Tripadvisor and Google. You submit each property once per site with your own ID. The first run loads its full history, and later runs send only new reviews by signed webhook, all in one format. See hotels and travel for the full list, or why hotel tech teams choose ReviewLake over Datashake.

How you use reviews is still governed by each site's terms and the laws where you operate, so check your use case with your own legal advisers.

Official API details checked against each platform's developer documentation on 11 November 2026.