HRS Reviews Scraper — Hotel Guest Reviews & Ratings
Pricing
$3.00 / 1,000 review rows
Every commented guest review of any HRS (hrs.com) hotel: 0-10 rating with twelve category votes, what guests liked and disliked, the hotel's replies, traveller type, stay dates and language, plus each property's averages by traveller type. Give HRS URLs or hotel ids. Pay per review.
HRS hotel pages, e.g. https://www.hrs.com/en/hotel/10520 — any language prefix works; the number is the hotel id.
[]HRS numeric hotel ids, e.g. 10520 — the number after /hotel/ in any hrs.com hotel URL. Faster than URLs for long lists; up to 20 ids go into one request.
[]0 = every commented rating the hotel has (HRS returns the whole list in one call; a busy hotel has a few hundred). N = only the first N in the chosen order — the cost control.
Which reviews come first before the cap applies. "Lowest rated" is the fastest way to a complaints feed; "Most recent" suits a schedule.
Leave empty for every guest. Otherwise keep only these HRS traveller types: BUSINESS, PRIVATE, YOUNG_COUPLE, MATURE_COUPLE, FAMILY_SMALL_CHILDREN, FAMILY_OLDER_CHILDREN, GROUP, CONFERENCE. Filtered reviews are never billed.
[]Leave empty for every language. Otherwise keep only comments written in these languages, as codes (de, en, fr, it, es, nl, pl, pt, ru, zh, tr, cs — or the 3-letter deu, eng, …) or names (German, English…). Filtered reviews are never billed.
[]0 = keep every review. 1-10 on the HRS scale (7 is a middling stay, below 6 is a bad one) = keep only reviews at or below it. Runs before billing, so a complaints feed pays for the complaints only.
HRS's list already contains only ratings with a written positive or negative, so this rarely removes anything; it guarantees every billed row carries text.
Language of the hrs.com page read for the hotel row (name, address, stars). Review comments keep the language their author wrote in.
Also emit one free row per hotel with name, stars, address, overall rating, rating count, recommendation rate, and the averages by traveller type and by category — and put the hotel name on every review row. Off = one request fewer per hotel, but no names.
How many proxy sessions (egress IPs) run in parallel. More is faster; each is paced separately.
Pace for each session. HRS answered 10 of 10 at 1/s on one residential IP in testing.
Apify Proxy RESIDENTIAL is required: both hrs.com and its ratings API answer 403 to datacenter IPs (Akamai and CloudFront). Residential traffic is small — one JSON call per 20 hotels plus one page per hotel for the hotel row.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}