Reputation monitoring
Pull the newest reviews for your property and read the disliked text first.
Booking.com data API · Reviews
Get the guest reviews for up to ten Booking.com properties: what the guest liked and disliked, the score, the date, the traveler type, the room they stayed in and the property's response. Sort and filter by Booking's own score bands.
Updated 21 October 2026
Pull the newest reviews for your property and read the disliked text first.
Read the poor and average reviews of the hotels you compete with and see what guests miss.
See which traveler types and rooms get the best and worst scores.
curl -X POST https://apiforagents.dev/v1/booking \
-H "Authorization: Bearer $AFA_KEY" \
-H "Content-Type: application/json" \
-d '{"op":"reviews","subjects":["https://www.booking.com/hotel/gb/<hotel-name>.html"],"sort":"newest","scoreBands":["average","poor"],"limit":25,"estimateOnly":true}'curl -X POST https://apiforagents.dev/v1/booking \
-H "Authorization: Bearer $AFA_KEY" \
-H "Content-Type: application/json" \
-d '{"op":"reviews","subjects":["https://www.booking.com/hotel/gb/<hotel-name>.html"],"sort":"newest","scoreBands":["average","poor"],"limit":25}'Everything you can send in one reviews call. Required inputs first.
| Input | Type | What it does |
|---|---|---|
| subjects * | text list | booking.com/hotel/<country>/<name> URLs. 1-10 items |
| sort | enum | |
| since | string | Stop at this date; applies with newest or oldest. YYYY-MM-DD |
| scoreBands | enum list | Booking's own 10-point score bands: superb 9+, good 7-9, average 5-7, poor <5. Not ratings. That name is a star filter elsewhere. |
| limit | integer | 1-100 |
The fields of every row, always present. Nothing is guessed: a value that could not be measured is null, and the answer's coverage says why.
| Field | Type |
|---|---|
| reviewId | string |
| reviewTitle | string |
| liked | string |
| disliked | string |
| rating | number |
| postedDate | string |
| language | string |
| travelerType | string |
| room | string |
| checkIn | string |
| checkOut | string |
| helpfulVotes | integer |
| photos | list of string |
| propertyResponse | string |
| reviewerName | string |
| reviewerLocation | string |
| reviewerAvatar | string |
| details | object |
details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.
Made-up names and values in the real field names, so you can see the shape before you spend anything.
| reviewerName | reviewerLocation | rating | reviewTitle | liked | disliked |
|---|---|---|---|---|---|
| Emma | Netherlands | 9 | Great location, friendly staff | Five minutes from the old town. | Coffee at breakfast. |
| Daniel | United States | 7.5 | Good value, small rooms | Clean and quiet. | Tiny bathroom. |
| Priya | India | 10 | Perfect stay | Everything, especially the staff. | Nothing. |
Pay as you go, in US dollars, per record. No subscription, nothing expires, $5 first top-up, and every new agent starts with $0.10 free.
| Request | Records | At the list price |
|---|---|---|
| One review | 1 | $0.0018 |
| 10 reviews | 10 | $0.018 |
| A full page | 100 | $0.18 |
These are per-record list prices. Some calls also carry a minimum, such as a page of search results, so a small request can cost more than the table shows. The quote ("estimateOnly": true) is free, gives the most your exact request can cost, and the charge then settles to what came back. Records that do not come back are refunded.
One row per review: the reviewer's name and location, the score, the review title, the liked and disliked text, the traveler type, the room, the posted date, the review id and photos. The property's response comes with it where there is one.
Up to ten booking.com/hotel/<country>/<name> URLs. Optional: sort (relevance, newest, oldest, rating_high or rating_low), a since date that applies with newest or oldest, score bands (superb, good, average or poor) and a limit of 1 to 100.
$0.0018 per review at the list price. A small call can carry a minimum, so quote first with "estimateOnly": true, which is free and is the most the call can cost. You pay for what comes back.
The playground runs any endpoint by hand: pick a platform and what you want from it, fill a short form named in plain words (or press Use sample input), see the free quote on the Run button, run it, then read the answer as a table or JSON and download it as CSV or JSON. The same call is written out as cURL, Python and Node while you type.
Why people pick API for Agents
API for Agents is independent and not affiliated with or endorsed by LinkedIn or any company named here. LinkedIn is a trademark of LinkedIn Corporation; other names belong to their owners. Public data only: nothing behind a login.