# /booking/hotels/reviews

`POST /api/booking/hotels/reviews`

Price: 5 credits

List guest reviews of a Booking.com property

## How to use it

List verified guest reviews for one Booking.com property, addressed either by its booking.com URL or by the '{country_code}/{alias}' pair from that URL. Every review carries the score out of 10, the headline and the separate positive and negative texts with their language, the reviewer's display name, country and traveller type, the room they stayed in with check-in/check-out dates and number of nights, the property's own reply, attached guest photos and the helpful-vote count. Reviews can be ordered by relevance, date or score and narrowed by free text, traveller type, score band, review language, review topic and the season of the stay. Topic ids come from 'review_topics' on the 'hotels' endpoint, requested in the same language, because topic ids differ per language.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `hotel` (string, required) — Booking.com property URL, or a '{country_code}/{alias}' pair taken from the property URL (examples: "us/millennium-broadway", "https://www.booking.com/hotel/nl/anantara-ghkrasnapolsky.html"; minLength: 3)
- `count` (integer, required) — Number of reviews to return (min: 1)
- `sort` (string) — Order the reviews are returned in (default: "most_relevant"; one of: "most_relevant", "newest_first", "oldest_first", "highest_scores", "lowest_scores")
- `text` (string, nullable) — Keep only reviews whose text contains this phrase
- `reviewer_type` (string, nullable) — Keep only reviews written by this traveller type (one of: "families", "couples", "groups_of_friends", "solo_travellers", "business_travellers")
- `score_bucket` (string, nullable) — Keep only reviews falling into this score band (one of: "wonderful_9_plus", "good_7_to_9", "fair_5_to_7", "poor_3_to_5", "very_poor_1_to_3")
- `season` (string, nullable) — Keep only reviews from stays in this period of the year (one of: "march_to_may", "june_to_august", "september_to_november", "december_to_february")
- `review_languages` (array) — Keep only reviews written in these ISO 639-1 language codes (default: []; examples: ["en","de"])
- `topic_ids` (array) — Keep only reviews mentioning these review topics, as returned in 'review_topics' by the 'hotels' endpoint for the same property and language (default: []; examples: [249,270])
- `language` (string) — Language of the returned texts (default: "en-us"; one of: "ar", "bg", "ca", "cs", "da", "de", "el", "en-gb", "en-us", "es", "es-ar", "es-mx", "et", "fi", "fr", "he", "hi", "hr", "hu", "id", "is", "it", "ja", "ko", "lt", "lv", "ms", "nl", "no", "pl", "pt-br", "pt-pt", "ro", "ru", "sk", "sl", "sr", "sv", "th", "tl", "tr", "uk", "vi", "zh-cn", "zh-tw")

## Response

### 200 — Successful Response

- `@type` (string) (default: "BookingHotelReview")
- `id` (string, required)
- `hotel_id` (integer, required)
- `score` (number, nullable)
- `review_title` (string, nullable)
- `positive_text` (string, nullable)
- `negative_text` (string, nullable)
- `language` (string, nullable)
- `created_at` (integer, nullable)
- `helpful_vote_count` (integer, nullable)
- `author_name` (string, nullable)
- `author_country` (string, nullable)
- `author_country_code` (string, nullable)
- `author_type` (string, nullable)
- `author_image` (string, nullable)
- `author_review_count` (integer, nullable)
- `author_joined_at` (integer, nullable)
- `traveller_type` (string, nullable)
- `room_id` (integer, nullable)
- `room_name` (string, nullable)
- `checkin_date` (string, nullable)
- `checkout_date` (string, nullable)
- `night_count` (integer, nullable)
- `stay_status` (string, nullable)
- `partner_reply` (string, nullable)
- `photos` (array) (default: [])

## Errors

### 422 — Validation Error

A requested topic id does not exist for this property in the requested language

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

Property not found

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.