# Expedia Reviews API (expedia.reviews)

- Canonical page: [https://everyinfra.com/en/expedia-api/reviews](https://everyinfra.com/en/expedia-api/reviews?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "expedia", "action": "reviews", "params": {...}}
- Price: $0.001389 per call ($1.39 per 1,000 requests); failed calls and empty results are not charged
- Returns: list, default 20, max 200 per call
- Mode: sync; add "mode": "async" for slow tasks

Expedia Reviews reads guest reviews of one hotel from its Expedia page, or the matching Hotels.com page, given as `url`. Each row carries the title and text, the rating with its word label, when the review was posted and when the guest stayed, the number of nights, the trip type and who the guest traveled with, the liked and disliked tags they ticked, and whether the stay was verified, along with the hotel's name, ID and average guest score. Hotel operators, revenue managers and travel researchers use it to follow guest sentiment, compare properties and track recurring complaints.

`stay_date` tells you when the guest actually stayed, which can be well before `posted_at`, so use it to judge how current an experience is. `verified` marks reviews from confirmed stays; unverified ones deserve less trust. `liked` and `disliked` are left out when the guest ticked nothing, so read a missing list as no tags rather than as missing data. `since` keeps only reviews posted from a given date on, which suits scheduled pulls that fetch only what is new.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=expedia&action=reviews

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | Accepts a single hotel page URL from Expedia or compatible Hotels.com links to fetch property profiles or reviews. It does not accept search result pages. Car rental queries must pass full search URLs via the keyword parameter instead. |
| reviews_from | not declared | no | not declared | Acts as a compatibility input for the review start date, accepting YYYY-MM-DD. When since is provided simultaneously, since takes precedence. It does not filter hotel stay dates. |
| since | not declared | no | not declared | Sets the lower date bound for hotel review queries using YYYY-MM-DD format, taking precedence over reviews_from. It does not filter hotel opening dates or car rental pickup periods. |
| sort | enum: most_helpful / newest / relevance / top_rated | no | not declared | Review order for `reviews`: `newest`, `relevance`, `top_rated`, or `most_helpful`. |
| limit | integer (1–200) | no | 20 | The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
| text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
| title | Title. null when the platform has no titles (for example text-only posts). |
| rating | Rating. **The scale varies by platform**: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards. |
| rating_scale | Maximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating. |
| rating_label | platform-native meaning |
| posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
| stay_date | platform-native meaning |
| author_name | Author's display name. |
| trip_type | platform-native meaning |
| stay_duration | platform-native meaning |
| traveled_with | platform-native meaning |
| verified | platform-native meaning |
| language | Content language code (for example zh, en) as judged by the platform; it can be wrong. |
| hotel_id | platform-native meaning |
| hotel_name | platform-native meaning |
| hotel_url | platform-native meaning |
| hotel_rating | platform-native meaning |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
| liked | platform-native meaning |
| disliked | platform-native meaning |
| image_urls | Array of image links in the platform's display order; absent when there are no images. |
| owner_response | The business's public reply to this review: text, author_name and posted_at; absent when there is no reply. |

## Example

```bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "expedia",
  "action": "reviews",
  "params": {
    "url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "expedia",
        "action": "reviews",
        "params": {
            "url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-10-24T18:28:34Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2 of 20. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "id": "req_…",
  "platform": "expedia",
  "action": "reviews",
  "results": [
    {
      "id": "70294428",
      "text": "Nice little motel with great location.",
      "title": "Nice little motel.",
      "rating": 8,
      "rating_label": "Good",
      "posted_at": "2014-05-08T00:00:00+00:00",
      "author_name": "•••",
      "trip_type": "",
      "traveled_with": "Traveled with family",
      "verified": true,
      "language": "en_US",
      "hotel_id": "20264",
      "hotel_name": "Channel Inn",
      "hotel_url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information",
      "hotel_rating": 6.6,
      "platform": "expedia",
      "rating_scale": 5
    },
    {
      "id": "70225987",
      "text": "Very smelly older gentalmen at front desk very bad attitude .",
      "title": "Poor condition",
      "rating": 2,
      "rating_label": "Terrible",
      "posted_at": "2014-05-06T00:00:00+00:00",
      "author_name": "•••",
      "trip_type": "",
      "traveled_with": "Traveled with partner",
      "verified": true,
      "language": "en_US",
      "hotel_id": "20264",
      "hotel_name": "Channel Inn",
      "hotel_url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information",
      "hotel_rating": 6.6,
      "platform": "expedia",
      "disliked": [
        "cleanliness",
        "staff & service",
        "property conditions & facilities"
      ],
      "rating_scale": 5
    }
  ],
  "count": 20,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### Which hotel link does `url` need?

The page of one hotel on Expedia, such as https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information, or the same hotel's page on Hotels.com. Search result pages list many hotels and do not work, and car rental links belong in Expedia Car rental quotes instead. The same hotel link also works with Expedia Details for the hotel's own record.

### What is the difference between `since` and `reviews_from`?

Both set the earliest review date, written as YYYY-MM-DD. `since` is the main parameter and `reviews_from` an alternative name accepted for compatibility; when you send both, `since` wins. They filter on when a review was posted, not on the guest's stay or a check-in date.

### How do I focus on reviews from travelers like my guests?

Group rows by `trip_type`, such as business, leisure or family, and by `traveled_with`, such as a partner, family, friends or traveling alone. Put rows where `verified` is true first, and set `sort` to `most_helpful` when you want the reviews other travelers found most useful at the top. `stay_duration` separates short stopovers from longer stays.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=expedia
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md
