Priceline Hotel Reviews Scraper avatar

Priceline Hotel Reviews Scraper

Pricing

Pay per usage

Go to Apify Store
Priceline Hotel Reviews Scraper

Priceline Hotel Reviews Scraper

Scrape Priceline hotel reviews, ratings & guest feedback at scale. Extract review text, scores, guest names, dates & metadata. Ideal for hotel reputation management, competitive benchmarking, sentiment analysis & travel market research. Structured JSON output.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 hours ago

Last modified

Share

Extract guest review data from Priceline hotel pages in a clean, analysis-ready dataset. Collect reviewer details, traveler type, review text, positive and negative remarks, category scores, and total review counts for hotel research, monitoring, and comparison.

Features

  • Hotel URL or ID input - Start with a Priceline hotel page or a hotel ID.
  • Guest review collection - Gather review text, reviewer metadata, ratings, and summary scores.
  • Pagination support - Collect more reviews with results_wanted and max_pages.
  • Clean output - Duplicate records and empty values are removed from saved records.
  • Flexible URL handling - Supports standard Priceline /relax/at/ hotel URL patterns.

Use Cases

Hotel Reputation Research

Track guest sentiment for a specific hotel. Review positive remarks, negative remarks, score patterns, and traveler profiles in one dataset.

Competitive Analysis

Compare hotels by guest feedback quality. Use scores for cleanliness, staff, location, and overall experience to evaluate strengths and weaknesses.

Travel Data Monitoring

Collect recent review samples for recurring reporting. Keep datasets small for fast checks or increase limits for deeper analysis.

Customer Experience Analysis

Study common complaints and praised amenities. Separate positive and negative remarks help teams classify recurring themes.


Input Parameters

ParameterTypeRequiredDefaultDescription
hotelUrlStringNo-Priceline hotel URL to scrape
hotelIdStringNo-Priceline hotel ID, used when URL is empty
results_wantedIntegerNo20Maximum reviews to collect
max_pagesIntegerNo5Maximum review pages to request
sortStringNo-Optional review sort value
proxyConfigurationObjectNoDisabledOptional proxy settings

Output Data

FieldTypeDescription
hotel_idStringPriceline hotel ID
source_urlStringSource hotel URL
pageNumberReview page number
current_pageNumberCurrent source review page
total_pagesNumberTotal available review pages
review_idStringUnique review ID
review_dateStringReview date
reviewer_nameStringReviewer display name
reviewer_locationStringReviewer location code
traveler_typeStringTraveler category
traveler_type_codeStringTraveler category code
review_textStringGeneral review text
positive_remarkStringPositive feedback
negative_remarkStringNegative feedback
score_overallNumberOverall review score
score_cleanlinessNumberCleanliness score
score_staffNumberStaff score
score_locationNumberLocation score
review_scoresArrayDetailed score labels and values
total_reviewsNumberTotal available reviews
review_summaryStringTotal review count label
review_summary_countNumberNumeric review summary count
review_summary_scoresObjectHotel-level summary scores
available_sort_optionsArraySort options shown for reviews
available_filtersArrayReview filter groups and options

Usage Examples

Scrape by Hotel URL

{
"hotelUrl": "https://www.priceline.com/relax/at/326303/from/20260716/to/20260801/rooms/1",
"results_wanted": 20
}

Scrape by Hotel ID

{
"hotelId": "326303",
"results_wanted": 50,
"max_pages": 5
}

Larger Review Collection

{
"hotelUrl": "https://www.priceline.com/relax/at/326303",
"results_wanted": 100,
"max_pages": 10
}

Sample Output

{
"hotel_id": "326303",
"source_url": "https://www.priceline.com/relax/at/326303/from/20260716/to/20260801/rooms/1",
"page": 1,
"current_page": 1,
"total_pages": 267,
"review_id": "5299215231",
"review_date": "Jun 2026",
"reviewer_name": "Minnie",
"reviewer_location": "ph",
"traveler_type": "Group Traveler",
"traveler_type_code": "GROUP",
"review_text": "Decent hotel but a little bit old and needs some update.",
"positive_remark": "Location",
"negative_remark": "During check-in: felt mocked by staff.",
"score_overall": 6,
"score_cleanliness": 7,
"score_staff": 8,
"score_location": 8,
"review_scores": [
{
"type": "CLEANLINESS",
"score": "7",
"label": "Cleanliness"
}
],
"total_reviews": 2668,
"review_summary": "5,108 Reviews",
"review_summary_count": 5108,
"review_summary_scores": {
"cleanliness": {
"score": 7.3,
"label": "Cleanliness"
}
}
}

Tips for Best Results

Start Small

  • Use results_wanted: 20 for test runs.
  • Increase limits after confirming the hotel has enough reviews.

Use Valid Hotel Pages

  • Use Priceline hotel pages that contain /relax/at/.
  • If a URL changes, provide the hotel ID directly.

Tune Pagination

  • Raise max_pages when collecting larger datasets.
  • Use results_wanted and max_pages to control collection size.

Integrations

Connect your data with:

  • Google Sheets - Review data and score tracking
  • Airtable - Searchable review databases
  • Webhooks - Send results to your system
  • Make - Automated reporting workflows
  • Zapier - Trigger alerts from new datasets

Export Formats

  • JSON - For developers and data pipelines
  • CSV - For spreadsheets
  • Excel - For business reporting
  • XML - For system integrations

Frequently Asked Questions

Can I use only a hotel ID?

Yes, you can provide hotelId without a URL.

Does it collect all reviews?

It collects up to your results_wanted and max_pages limits.

Why are some fields missing?

Fields are omitted when Priceline does not provide a value for that review.

Can I collect reviews from multiple hotels?

Run the actor once per hotel to keep datasets clearly separated.

What URL formats are supported?

Priceline hotel URLs using /relax/at/326303 and dated variants are supported.


Support

For issues or feature requests, contact support through the Apify Console.

Resources


This actor is designed for legitimate data collection purposes. Users are responsible for ensuring compliance with website terms of service and applicable laws. Use data responsibly and respect rate limits.