# Booking Reviews API (booking.reviews)

- Canonical page: [https://everyinfra.com/en/booking-api/reviews](https://everyinfra.com/en/booking-api/reviews?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "booking", "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 100 per call
- Mode: sync; add "mode": "async" for slow tasks

Booking Reviews reads guest reviews of one property on Booking, given the property's page link as `url`. Booking asks guests to write what they liked and what they did not in separate boxes, so each row carries `text_positive` and `text_negative` instead of a single body, along with the title, the score, the month of the stay, the room type and number of nights, the guest's country and traveler type, and the property's reply. Hotel managers, revenue teams and analysts use it to find what guests praise and complain about, compare guest segments and see how the property responds.

Either box can be empty, so treat a missing negative as nothing written, not as praise. Scores are out of 10 on Booking; convert with `rating_scale` before you compare them with five-star sites. `stay_date` gives the month the guest actually stayed, the better guide to how current a review is. The request has no filters beyond the link and `limit`, so sort and filter the rows after you fetch them.

## Health

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

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | Specifies the full URL to a single property page, preferably using the /hotel/ path format. Used by profile to fetch details, reviews to retrieve property reviews, and prices to check room rates. Destination search URLs are not supported. |
| limit | integer (1–100) | no | 20 | The most rows to return in this call, an integer from 1 to 100. 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. |
| title | Title. null when the platform has no titles (for example text-only posts). |
| text_positive | The positive part of the review: Booking asks reviewers to fill in what they liked and disliked separately. |
| text_negative | The negative part of the review. Either part can be empty. |
| 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. |
| 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 | The month the reviewer stayed, useful for judging how recent the review is. |
| author_name | Author's display name. |
| author_country | The reviewer's country. |
| traveler_type | Type of trip (business, couple, family, solo and so on); use it to filter reviews from guests like yours. |
| room_name | Room type name. |
| nights | Number of nights used for this lookup. |
| language | Content language code (for example zh, en) as judged by the platform; it can be wrong. |
| owner_response | The business's public reply to this review: text, author_name and posted_at; absent when there is no reply. |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |

## 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": "booking",
  "action": "reviews",
  "params": {
    "url": "https://www.booking.com/hotel/jp/park-hyatt-tokyo.html"
  }
}'
```

```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": "booking",
        "action": "reviews",
        "params": {
            "url": "https://www.booking.com/hotel/jp/park-hyatt-tokyo.html",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-09-26T08:56:04Z. `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": "booking",
  "action": "reviews",
  "results": [
    {
      "id": "608726deed389acf",
      "rating": 5,
      "posted_at": "2026-09-23T12:06:15+00:00",
      "stay_date": "2026-09-19T00:00:00.000Z",
      "author_name": "•••",
      "room_name": "King Room with City View",
      "platform": "booking",
      "rating_scale": 10
    },
    {
      "id": "5970507e264636a7",
      "rating": 5,
      "posted_at": "2026-09-15T10:59:06+00:00",
      "stay_date": "2026-08-14T00:00:00.000Z",
      "author_name": "•••",
      "room_name": "Deluxe Room with Two Double Beds",
      "platform": "booking",
      "rating_scale": 10
    }
  ],
  "count": 20,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### Why are there two text fields instead of one?

Booking collects the good and the bad in two separate fields of its review form, and the capability keeps them apart in `text_positive` and `text_negative`; either can be empty. The split saves work in sentiment analysis: mine complaints from the negative field directly instead of classifying whole reviews, and count empty fields separately.

### How do I read reviews from one type of guest?

Group rows by `traveler_type`, such as business travelers, couples, families or solo travelers, and by `room_name` when one room category matters. `author_country` shows where guests come from, and `nights` the length of the stay, which helps tell short business trips from longer holidays.

### Can I get reviews in a single language?

Not through the request, which takes the property link and `limit` but no language filter, and nothing here translates review text. Each row's `language` is the code Booking assigns, which can be wrong, so run your own language detection when the split matters, for example before you count complaints by market.

## Also

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