/hostelworld/properties/reviews

POST /api/hostelworld/properties/reviews

Price: 1 credit

Get guest reviews for a Hostelworld property by property id (or property URL), newest first. Each review has the review text, date, language, machine-translation flag, an optional property-owner reply, a rating breakdown (overall, value, safety, location, staff, atmosphere, cleanliness, facilities), the author (nickname, gender, nationality, profile image, total reviews written) and group/trip context (group type, age range, trip types).

How to use it

Fetch guest reviews for a single Hostelworld property by numeric property id or a property URL, ordered newest first. Each item has id, text, created_at (review date), language_code, is_machine_translated, owner_comment (optional owner reply), rating (overall, value, safety, location, staff, atmosphere, cleanliness, facilities, all 0-100), author (id, name, gender, country, country_code, image, review_count) and group (type, age, trip_types). Set count to the number of reviews you want.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Hostelworld property id or a property URL containing it (examples: "39493", "https://www.hostelworld.com/hostels/p/39493/onefam-waterloo/"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "HostelworldReview")
• id string required
• text string nullable
• created_at string nullable
• language_code string nullable
• is_machine_translated boolean nullable
• owner_comment string nullable
• rating object nullable
  • @type string (default: "HostelworldReviewRating")
  • overall integer nullable
  • value integer nullable
  • safety integer nullable
  • location integer nullable
  • staff integer nullable
  • atmosphere integer nullable
  • cleanliness integer nullable
  • facilities integer nullable
• author object nullable
  • @type string (default: "HostelworldReviewAuthor")
  • id string nullable
  • name string nullable
  • gender string nullable
  • country string nullable
  • country_code string nullable
  • image string nullable
  • review_count integer nullable
• group object nullable
  • @type string (default: "HostelworldReviewGroup")
  • type string nullable
  • age string nullable
  • trip_types array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 (well-formed but nonexistent property id) 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 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 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 Wait at least 30 seconds, then retry.

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