Booking Reviews API

Q: 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.

Q: 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.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Collect guest reviews of a Booking.com property, with liked and disliked text kept apart, score, stay month, traveler type, room and any hotel reply. Either half can be empty, and the batch may not include every review.

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.

Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Booking Reviews endpoint (booking/reviews).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to booking and action to reviews, and put the parameters inside params.
- Required parameters:
  - url: 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.
- Optional parameters:
  - limit: 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. (default: 20)
- Returns a list of records. Main fields of each record: id, title, text_positive (The positive part of the review: Bookin…), text_negative (The negative part of the review), rating, rating_scale, posted_at, stay_date (The month the reviewer stayed, useful f…), author_name, author_country (The reviewer's country), traveler_type (Type of trip (business, couple, family,…), room_name (Room type name); 15 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=booking.
- Example request body:
{
  "platform": "booking",
  "action": "reviews",
  "params": {
    "url": "https://www.booking.com/hotel/jp/park-hyatt-tokyo.html"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`booking`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`reviews`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	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`	body.params	`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.

Code samples

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"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Real response

Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json

{
  "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": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

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).

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.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

Booking: Guest Reviews and Sub-Category Ratings ↗
Booking documentation notes that overall review scores and individual category scores are submitted independently. This references official website framing; review scale dimensions for this API action must still be checked against each input shape, and citing this link does not verify that normalization has been validated.
Checked 2026-09-04