Priceline Hotel Scraper

Extract hotel availability and pricing from Priceline.com at scale. Give it a destination and dates and it returns every available hotel with nightly + total prices, star levels, guest-review scores, amenities, GPS coordinates and neighborhoods — optionally enriched with per-hotel guest reviews. Built on Priceline's official GraphQL API, so output is clean, structured JSON, not brittle HTML scraping.

Who it's for

• Travel & OTA analysts / revenue managers — benchmark hotel rates across cities, track supply, monitor rate parity vs other channels.
• Investors & market researchers — hotel pricing and guest-sentiment data per market and date range.
• PropTech / travel-app developers — a stable JSON feed of hotel inventory to power apps, dashboards and price-comparison tools.
• Agencies & data teams — bulk hotel datasets with reviews for any US or international destination.

What you get (output fields)

Field	Description
hotel_id	Priceline hotel id
name	Hotel name
star_level	Star rating text (e.g. "3-Star Hotel")
neighborhood	Neighborhood / area
brand, brand_owner	Hotel brand and parent group
latitude, longitude	GPS coordinates
price_amount, price_currency	Nightly headline price
total_price_amount	Total stay price incl. taxes & fees
price_strike, price_savings	Was-price and savings when discounted
review_score_overall, review_scores	Guest rating (0–10) + sub-scores
review_count_label	Number of reviews
amenities, themes	Amenity list and property themes
images	Hotel photo URLs
cancellation_policy, payment_disclaimer	Booking terms
reviews	Guest reviews (when Include guest reviews is on)
url	Direct hotel page URL
scraped_at	ISO-8601 scrape timestamp

Use cases

• Rate benchmarking — pull the full hotel list for a city + date pair on a schedule and track how prices move over time.
• Market supply analysis — count hotels, star tiers and brands per destination.
• Guest-sentiment research — combine review scores and review text across a market.
• Price-comparison products — feed Priceline inventory into a multi-OTA comparison app.

Input

Field	Type	Default	Description
destination	string	"New York"	City name (auto-resolved) or numeric geo id
checkIn	string	+30 days	Check-in YYYY-MM-DD
checkOut	string	+32 days	Check-out YYYY-MM-DD
adults	integer	2	Adult guests
rooms	integer	1	Rooms
sort	enum	RECOMMENDED	RECOMMENDED, PRICE, REVIEW_SCORE
maxItems	integer	100	Stop after N hotels
includeReviews	boolean	false	Add per-hotel guest reviews
maxReviews	integer	10	Reviews per hotel
currency	string	USD	ISO 4217 currency
proxyConfiguration	object	Apify residential	Proxy settings

Example input

{
    "destination": "Miami",
    "checkIn": "2026-09-01",
    "checkOut": "2026-09-03",
    "adults": 2,
    "sort": "PRICE",
    "maxItems": 100
}

Example output row

{
    "hotel_id": "40730",
    "name": "New Yorker by Lotte Hotels",
    "star_level": "3-Star Hotel",
    "neighborhood": "Midtown West - Hell's Kitchen",
    "latitude": 40.7522,
    "longitude": -73.9935,
    "price_amount": "338.26",
    "price_currency": "USD",
    "total_price_amount": "863.70",
    "review_score_overall": "7.7",
    "review_count_label": "1,338 Reviews",
    "amenities": ["Free Internet Access", "Fitness Center"],
    "url": "https://www.priceline.com/relax/at/40730/from/20260901/to/20260903/rooms/1/adults/2",
    "scraped_at": "2026-07-21T00:00:00Z"
}

Scheduling & integrations

Run it on a schedule to build hotel price-history datasets, or trigger it via the Apify API and pipe results to Google Sheets, S3, a database, or a webhook. Every field above is available in JSON, CSV, Excel and HTML exports.

AI assistants (MCP)

Prefer to query Priceline live from Claude, ChatGPT or Cursor? Use the companion Priceline Travel MCP Server actor to search hotels and flights as MCP tools.

FAQ

Which destinations are supported? Any city Priceline covers, worldwide — pass a city name (auto-resolved) or a Priceline geo id.

How fresh is the data? Live — every run queries Priceline in real time for your exact dates.

Are opaque "Express Deal" hotels included? They appear as rows with a hidden name (Priceline only reveals it after booking); their pricing is still returned.

Is this reliable? It uses Priceline's official API endpoints rather than HTML scraping, so the schema is stable and results are consistent.

Is scraping this legal? The actor collects publicly available listing data. You are responsible for using the data in line with applicable laws and Priceline's terms.