Expedia Reviews API: How to Access and Use Expedia Guest Review Data

Expedia has two official review APIs, and both are for partners.
Rapid, Expedia's program for travel sellers, includes a Guest Reviews API for showing reviews in a booking flow, and the Lodging Supply API lets properties and their connectivity providers read and answer their own reviews.
If you need reviews as data for a portfolio, a comp set, or a market study, neither one was built for you.
If you've searched for an Expedia reviews API and landed on the "publicreview" endpoint, that's the undocumented internal route some developers reverse-engineer.
It returns review data, but it's unsupported, has no SLA, and has broken without warning before.
Not something to build on.
Here's the thing worth knowing up front: Expedia is one of the largest OTAs for North American hotel bookings.
For any property with meaningful US or Canadian guest exposure, Expedia reviews are a core data source, often second or third behind Google.
Outside those partner programs, three paths exist to get that data: Expedia Partner Central (manual, your own property only), unofficial endpoints and scrapers (fragile), and third-party data providers that return Expedia review data as structured JSON.
This guide covers all three, and what each one actually gets you.

Key Takeaways

• Expedia's review APIs are partner-only. Rapid's Guest Reviews API serves travel sellers, and the Lodging Supply API serves properties and their connectivity providers. Neither is open to a team that only needs the data.
• The "publicreview" endpoint is not a real option. It's an undocumented internal Expedia route. No support, no SLA, breaks without notice. Fine for a one-off experiment, wrong for production.
• Three paths work: Partner Central (manual, no export), unofficial endpoints and scrapers (high-maintenance), and third-party data providers that return structured JSON.
• Expedia's review schema is leaner than Booking.com's. You get the essentials: full review text, a 10-point rating with a label, reviewer name, and date. Public Expedia reviews carry no positive/negative split, and third-party access returns no sub-category scores.
• A data API delivers Expedia reviews as structured JSON alongside Booking.com, Agoda, TripAdvisor, Airbnb, and Google Hotels through one integration.

Why Expedia Review Data Matters

Expedia is the OTA that North American hotels can't ignore.
For properties in the US, Canada, and Mexico, it's often the largest review source after Google, and for resorts and conference hotels it can outrank TripAdvisor on volume.
The guest profile is part of why it's worth tracking separately.
Expedia skews toward business and frequent travelers more than Booking.com (leisure-heavy) or Agoda (Asia-Pacific focused).
That shows up in the review text.
Business guests write about location, check-in speed, Wi-Fi reliability, and breakfast more than they write about the pool.
If your hotel chases corporate accounts or conference groups, Expedia is your clearest read on how that segment actually experienced the stay.
A hotel that monitors only Booking.com is reading one slice of its guests.
Adding Expedia fills in the North American and business-traveler slice that the other platforms underweight.

Does Expedia Have a Public Reviews API?

Not a public one, but Expedia runs two partner review APIs.
Rapid's Guest Reviews API returns up to 100 reviews per property with the overall rating, title, text, reviewer name, stay and submission dates, trip reason, and the property's response.
It's built for Rapid partners showing reviews in their own shopping and booking flow under Expedia's launch requirements, and reviews can be cached for up to 48 hours.
The Lodging Supply API's reviews capability lets properties and their connectivity providers retrieve approved reviews with reservation IDs, pull aggregated category ratings, and post responses, with webhooks for new reviews.
Both are well built for their owners, and neither is open to a team that only needs the data.
Then there's the "publicreview" endpoint.
Some developers have found internal Expedia endpoints that return review data, sometimes referenced as the publicreview API.
It exists, and it works until it doesn't.
It's undocumented, unsupported, carries no guaranteed availability, and has changed without notice in the past.
For a one-time research pull it might get you a snapshot. For anything that needs to run next month, it's a foundation that can disappear overnight.
Expedia Partner Central is the third piece people ask about.
It's the property management portal for registered Expedia partners, and it shows guest reviews in the dashboard.
You can read and respond to them in the UI, and automating that for your own property goes through a connectivity provider on the Supply API.
The bottom line: official access follows the partnership, so reviews for hotels you don't sell or manage come from a third-party provider or a scraper.

Three Ways to Access Expedia Review Data

Option 1: Expedia Partner Central (Manual)

Registered Expedia partners can view guest reviews in Partner Central under the Reviews section.
You can read each review and respond to it, one at a time.
For your own properties, a connectivity provider on the Supply API can automate the same work.
Good for an individual property owner keeping an eye on reviews and replying to them.
It falls apart past a handful of properties, and it gives you nothing you can feed into software.

Option 2: Unofficial Endpoints and Scraper Tools

The publicreview endpoint and general-purpose scraper tools (Apify, Outscraper, custom Python) can pull review data off Expedia property pages.
If you searched "how to get Expedia reviews" and found a code snippet hitting an undocumented endpoint, this is that route.
Good for a quick one-off pull, research, or a prototype.
The catch is maintenance.
Undocumented endpoints change shape without warning, and HTML scrapers break whenever Expedia updates its page structure.
Expedia's bot detection is less aggressive than Booking.com's, so scraping survives a bit longer here, but "longer" still means ongoing upkeep.
There's also no multi-OTA consolidation: every platform you add is a separate scraper to build and babysit.

Option 3: A Property Data API

Third-party data providers run a maintained API that handles the extraction and returns Expedia reviews as structured JSON.
StayAPI is one example.
One API key covers Expedia alongside Booking.com, Agoda, TripAdvisor, Airbnb, and Google Hotels.
You send a property ID → you get the review schema back the same way every time, no endpoint to maintain.
Good for revenue management agencies tracking multi-OTA portfolios, developers building review dashboards, and hotel chains watching performance across every platform at once.

How the Three Options Compare

	Partner Central	Unofficial Endpoints	Data API (StayAPI)
Reliability	High (official UI)	Low (breaks without notice)	High (API-based)
Update frequency	Manual	Manual	Real-time, on request
Bulk export	No	Yes (when it works)	Yes (structured JSON)
Multi-OTA support	No	Per-platform setup	Yes (6 OTAs, one key)
Technical skill	None	High	Low (REST API)
Production-ready	No	No	Yes

What Expedia Review Data Looks Like

Worth setting expectations here, because Expedia's review data is leaner than Booking.com's.
You won't get a pre-labeled positive/negative split or sub-category scores.
What you do get is the core of a review, cleanly structured.

Fields Available

Field	Example Value	Description
Review text	"Great staff and tidy room"	Full guest comment (can be empty)
Overall rating	"8/10 Good"	10-point score with a text label
Reviewer name	"Simon"	Guest's display name
Review date	"Dec 18, 2025"	Date the review was posted
Property ID	"1582716"	Expedia's identifier for the property
Owner response	{"text": "...", "published_date": "Jan 11, 2026"}	The property's reply, or null

A correction on a common assumption: Expedia uses a 10-point rating scale, returned as a string like "10/10 Excellent" or "8/10 Good", not the 5-star scale people sometimes expect.
The rating ships with both the number and Expedia's word label, so you can read it either way.

What Expedia Data Is (and Isn't) Good For

The honest tradeoff: Expedia gives you the review text and a calibrated rating, and not much metadata around it.
There's no positive/negative comment split like Booking.com's, so separating praise from complaints means running your own sentiment analysis on the text field.
There are no sub-scores for cleanliness or service via third-party access.
That's fine for most use cases.
The full review text plus a normalized 10-point rating and a date is enough to track reputation trends, run text analysis, and benchmark against a comp set.
You're trading metadata richness for coverage of a market the other OTAs underrepresent.

Sample API Response

Here's what the review data looks like from StayAPI's Expedia reviews endpoint:

{
  "property_id": "1582716",
  "reviews": [
    {
      "id": "694282f4d4d0dc6c19a2e682",
      "rating": "8/10 Good",
      "text": "Great staff and tidy room",
      "reviewer_name": "Simon",
      "review_date": "Dec 18, 2025",
      "owner_response": {
        "text": "Thank you for your review, we appreciate it!...",
        "published_date": "Jan 11, 2026"
      }
    }
  ],
  "total_count": 5,
  "page": 0,
  "per_page": 5,
  "has_more": true
}

That's the first of 5 reviews in the response, pulled on September 29, 2026 for a hotel in Rovaniemi, Finland.
total_count counts the reviews in the current page, so read has_more to decide whether to request the next one.

Use Cases for Expedia Review Data

These lean on Expedia's strength: North American and business-traveler coverage.
- North American reputation monitoring. For hotels with significant US or Canadian guests, Expedia is a primary review source. Pulling rating and text on a schedule catches trends that a weekly manual check misses.
- Sentiment analysis on review text. Expedia gives you the full comment without a pre-labeled split, so it's a clean input for NLP. Run topic and sentiment extraction over the text to surface business-guest pain points like slow check-in or weak Wi-Fi. (See our guide to hotel review sentiment analysis.)
- Cross-OTA review consolidation. Pull Expedia reviews into the same schema as Booking.com, Agoda, TripAdvisor, Airbnb, and Google Hotels. For North American properties, Expedia often carries more reviews than TripAdvisor.
- Competitive intelligence. Track a competitor's Expedia rating and how fast their review count climbs. A rival adding 50 Expedia reviews a month while you add 10 is a signal worth acting on.
- Rapid prototype validation. Developers building travel apps can pull Expedia review data to test features without negotiating an Expedia Rapid API agreement first.

Getting Started with StayAPI

1. Sign up at stayapi.com. No credit card required, no Expedia Rapid API agreement needed.
2. Find your Expedia property ID. It's the number after the h in an Expedia property URL, for example https://www.expedia.com/h1582716.Hotel-Information → 1582716.
3. Make your first call:

curl -X GET "https://api.stayapi.com/v1/expedia/hotel/reviews?property_id=1582716&page=0&per_page=5" \
  -H "x-api-key: YOUR_API_KEY"

You pass the Expedia property ID and your API key → you get structured JSON back with the review text, rating, reviewer name, and date.
Pages are 0-indexed and return up to 5 reviews each, so loop page while has_more is true.
The default order is recommended; pass sort=recent_desc for newest-first pulls.
For the full endpoint reference, see the Expedia reviews API documentation.
Pipe the output into your own system, Google Sheets, Looker Studio, Power BI, or no-code tools like N8N and Make.com.
For teams wanting a walkthrough, book a demo call.

FAQ

Does Expedia have a reviews API?

Not a public one.
Rapid's Guest Reviews API serves travel sellers showing reviews in their booking flow, and the Lodging Supply API lets properties and their connectivity providers read and respond to their own reviews.
For a team that only needs the data, a third-party provider like StayAPI is the production-viable route.

What is the Expedia publicreview API?

It's an undocumented internal Expedia endpoint that some developers have reverse-engineered to read review data.
It has no official support, no SLA, and has broken without notice.
It can work for a quick experiment, but it's not something to build a product on.

How do I get Expedia hotel review data?

For your own property, Partner Central or a connectivity provider on the Supply API.
For any property, unofficial endpoints and scrapers (unreliable, high-maintenance) or a data provider like StayAPI that returns structured JSON in real time.

What fields does Expedia review data include?

The core review fields: full review text, an overall 10-point rating with a label (like "8/10 Good"), the reviewer's name, the review date, and the property's response when there is one.
Pre-labeled positive/negative splits and sub-category scores are not available through third-party access.

What rating scale does Expedia use?

A 10-point scale, returned as a string with a label, such as "10/10 Excellent" or "8/10 Good."
When you consolidate Expedia data with other OTAs, you'll want to normalize it against TripAdvisor's 5-point and Booking.com's 10-point scales.

How often does Expedia review data update via StayAPI?

It's real-time.
You make a call, you get current data back.
There's no batch sync or refresh schedule to wait on.

Can I get Expedia reviews for competitor properties?

Yes.
Any public Expedia property can be tracked, not just your own.