Booking.com attraction reviews

GET https://api.api.sh/booking/v1/attraction-reviews
1 credit / call travel & events try it in the playground →

Reviews of an attraction: rating, text, language, date, traveler type, author and country, supplier response and photos, plus the total and every sort and filter option with counts. Pass next_page as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
id string Attraction id (the id from attractions or attraction). Example: PRe4kSVWXdrD
url string Attraction URL instead of id.
page integer Page (default 1).
limit integer Reviews per page (default 10, up to 50).
sort most_relevant | newest | oldest | highest_rating | lowest_rating most_relevant (default), newest, oldest, highest_rating or lowest_rating.
score integer Only reviews with this star score (1-5).
time_of_year string Q1, Q2, Q3 or Q4.
language string Review language codes, comma-separated.
q string Text the reviews contain.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/booking/v1/attraction-reviews?id=PRe4kSVWXdrD" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.