Priceline Hotel Reviews Scraper
Pricing
from $3.00 / 1,000 hotel extracteds
Scrape hotel reviews from Priceline: review text, pros/cons, reviewer info, and individual ratings. Get guest scores, category ratings, GPS coordinates, and neighborhood data for 107 cities or specific URLs. Export data, run via API, schedule runs, or integrate with other tools.
All notable changes to Priceline Hotel Reviews Scraper are documented here.
maxHotels/minStars/minScore filters moved to a dedicated Search filters section.ACTOR_VERSION/dataVersion → 0.7.1; package.json synced. No dataset/output-shape change.inputType: "country"). Pick a country from a 49-country dropdown (searchCountry) and the scraper pulls hotels from that country's vetted cities, merges them (deduplicated by hotel ID), and applies the same minStars/minScore/maxHotels filters as City Search. A country is a static group of the existing 107 vetted cities (e.g. France → Paris, Nice, Lyon; United States → its 25 mapped cities), so coverage is reliable. Priceline has no country-level hotel geo, so a dynamic autocomplete approach was evaluated and rejected as too fragile (keyword-match false positives); the static mapping mirrors how City Search already works.ACTOR_VERSION/dataVersion → 0.7.0; actor.json version → 0.7; package.json synced. No dataset/output-shape change.maxHotels from 100 to 10. Apify's automated quality tests run the prefilled City Search input and cap each run at 5 minutes; processing 100 hotels sequentially took ~13 minutes and timed out, which flagged the Actor "Under maintenance". The default 10-hotel city pull now finishes in about two to three minutes, well inside the limit. Set maxHotels higher (up to 500) to scrape a full city. Reviews per hotel are unchanged.ACTOR_VERSION/dataVersion → 0.6.2; package.json synced. No dataset/output-shape change.OUTPUT run summary now reports a dedicated incompleteCount, and errorCount no longer counts _incomplete rows. Previously a hotel pushed as _incomplete (degraded data — validation failed or reviews unrecoverable, never charged) was lumped into errorCount, overstating failures for a run whose profiles were otherwise usable. errorCount now counts only genuine fetch/extraction errors. Dataset row shape is unchanged.types.ts.ACTOR_VERSION/dataVersion → 0.6.1; package.json synced.ratings.travelerTypes field: review counts by guest segment (Traveling as Couple, Family with Young Children, Group, Solo, Business, Senior, …), mapped from Priceline's reviewRatingSummary. No extra network cost — the data was already fetched per hotel and previously discarded. Priceline's "Total" row is excluded (it counts rating responses, not text reviews, and its sum differs from totalReviewCount).ratings.distribution and ratings.aiSummary. Both were always null: a verification spike (2026-06-22) confirmed Priceline's API exposes neither a rating histogram nor an AI summary. Downstream consumers referencing these columns should remove them; the values were never populated.ACTOR_VERSION/dataVersion → 0.6.0; actor.json version → 0.6; package.json synced.ACTOR_VERSION/dataVersion → 0.5.7; package.json synced. No dataset/output-shape change.401/402 (bad key / out of credits) now abort the run early with a structured ConfigError record and exit SUCCEEDED, instead of being treated as a success body that produced per-hotel parse noise across every hotel._incomplete and not charged. A hotel that genuinely has zero reviews is still a billable extraction.ParserDrift when a fetched page parses to zero hotels (a soft-block / drift) instead of the misleading "no hotels found" — Priceline city IDs are audited/valid, so zero parsed is never a genuine empty city.ACTOR_VERSION/dataVersion → 0.5.6; package.json synced. No dataset/output-shape change.alternativeUrl fallback that left 422 as a dead-end null.reviewId across pages. Overlapping pages (common with sort=null while new reviews arrive mid-walk) previously inflated review counts and distorted the pagination stop condition. Reviews without a reviewId are always kept (cannot be safely deduped).GRAPHQL_HEADERS constant. ZenRows only forwards caller headers with custom_headers=true (never set); the constant had zero references.ACTOR_VERSION/dataVersion → 0.5.5; package.json synced.null in the mapper and never present in the getHotelDetails response: chain, brand, propertyType, yearBuilt, yearRenovated. They promised data the API does not provide. (Hotel brand/type exist in Priceline's listings query, not details — a future coverage sprint could probe adding them.) ACTOR_VERSION/dataVersion → 0.5.4. Audit 2026-06-01 finding X-3._incomplete (pushed but NOT charged): ratings.totalReviewCount min(1)→min(0) (a new hotel with a complete profile and zero reviews is valid, chargeable data) and review overallRating min(1)→min(0) (a single review lacking an "overall" score entry — mapped to 0 — no longer fails the whole hotel). A 99-good-review hotel with one partial review was billing $0. Audit 2026-06-01 finding. ACTOR_VERSION/dataVersion bumped to 0.5.3.roomTypes, nearbyPOIs, mandatoryFees fields dropped from output. These were declared in the HotelDetail type and always shipped as empty arrays ([] as never[]), advertised internally as "Phase 3+" deliverables that were never implemented. Rather than continue to expose placeholder columns, the fields are removed entirely. Each of them requires a separate GraphQL query against Priceline; if/when implemented, they will be added back behind a feature flag with real data.roomTypes, nearbyPOIs or mandatoryFees on output rows must update their parsers; the columns will no longer appear in JSON / CSV / Excel exports.ACTOR_VERSION bumped to 0.5.0; actor.json version: "0.5"; package.json synced. dataVersion on every output row now reads "0.5.0".maxReviewsPerHotel, and the documented value 0 (advertised as "all available reviews") returned 0 due to a guard inversion. Now: 0 means "fetch all up to a 1000-review safety cap"; any positive value loops through pages of 100 until the target is reached or totalPages is exhausted.reviewsTruncated: true flag on hotel rows where the actual reviews count is less than totalReviewCount (clear signal for downstream consumers that there are more reviews than fetched).maxReviewsPerHotel=0 would issue ~10 ZenRows calls per hotel.reviews field now populates with individual guest reviews. The legacy hotelDetails.guestReviews field is permanently null in Priceline's API; the scraper now calls the dedicated getReviewsByHotelIds GraphQL operation (same endpoint, same proxy) that powers Priceline's "Show All Reviews" modal. Each review carries text, pros, cons, overallRating, reviewer.{name, location, travelerType}, reviewDate, and a server-side reviewId when provided.HOTEL_REVIEWS_QUERY constant in src/constants.ts — the reverse-engineered getReviewsByHotelIds operation (verbatim from assets.pclncdn.com/web/relax/.../RELAX.main.*.js).fetchHotelReviews(proxy, hotelId, { limit, offset }) in src/priceline-api.ts — limit capped at 100 to avoid oversized responses; uses 1-indexed offsets (matches the bundle defaults).mapReviewsV2(rawReviews) in src/parsers/graphql-mapper.ts — maps the new GraphQL response shape (scores[], reviewerInfo, entryDate) onto the existing HotelReview interface; preserves server-side reviewId and falls back to text-hash when absent.main.ts reviews step decoupled from fetchHotelDetails: after profile mapping, it calls fetchHotelReviews (best-effort, never fails the hotel) and only when maxReviewsPerHotel > 0. PPE charging is unchanged: still a single Actor.pushData(hotel, 'hotel-extracted') per hotel.mapReviews is retained for backwards compatibility but no longer called from main.ts.ACTOR_VERSION bumped to 0.4.4; package.json + package-lock.json synced.amenities: array of structured amenity objects (code, name, type, free, displayable) mapped from hotelFeatures.hotelAmenities. Was previously hardcoded [].amenitiesFlat: array of highlighted amenity codes mapped from hotelFeatures.highlightedAmenities. Was previously hardcoded [].highlights: array of feature strings mapped from hotelFeatures.features (e.g., "Daily disinfection", "Family rooms"). Was previously hardcoded [].photos: array of photo objects with thumbnail and full URLs mapped from hotel.images. Was previously hardcoded [].policies: object with checkInTime, checkOutTime, petDescription, childrenDescription, importantInfo[] mapped from hotel.policies. Was previously hardcoded null..passthrough() keeps backward compatibility). The fields were already arriving in the API response and were being silently dropped during mapping.dataVersion bumped from 0.4.0 to 0.4.3 to reflect the enriched payload.reviews returns [] because Priceline's hotelDetails GraphQL endpoint now returns guestReviews: null. Recovering individual reviews requires reverse-engineering a separate reviews endpoint and is out of scope for this release.roomTypes, nearbyPOIs, mandatoryFees remain empty placeholders — they require additional GraphQL queries (deferred).chargedCount value. Apify SDK v3.7.2 doubles chargedCount when pushing to the default dataset with an explicit event (auto-schedules both hotel-extracted and synthetic apify-default-dataset-item), which made the log read chargedCount=2 and suggest double-billing. Only the explicit hotel-extracted event is billed by the Platform; the synthetic dataset event is local-only tracking. No revenue impact, only a cosmetic log fix.etc. from scheduling FAQInitial Store release. Pay-per-event pricing at $0.005 per hotel extracted. GraphQL-based extraction with city search, hotel URL, and hotel ID input modes.