Booking.com scrapers compared

Cost per place scraped. This cost is applied for each successfully scraped property or place returned in the results.

• Add-on: Additional hotel data (additional-details-scraped)

Cost per review scraped. This cost is applied for each successfully scraped review returned in the results.

One itinerary, price-calendar day or explore destination row. Error rows and empty results are always free. No run fee, no search fee, no proxy fee.

A hotel listing with price, rating, amenities, and availability

Charged per accommodation returned (the property result with live price and links).

• Hotel details (hotel-details)
• Room details (room-details)
• Review (review)
• Nearby places (surroundings)
• Review scores (review-scores)

One search result with price, matched room, rating, location and photo. Error rows are free.

• Hotel details (hotel)
• Room (room)
• Rate (rate)
• Review (review)
• Calendar day (calendar-day)

Cost per place scraped. This cost is applied for each successfully scraped property or place returned in the results.

Charged for each guest review extracted.

• Hotel summary row (hotel-summary)

Single result in the default dataset.

• Record scraped (Review_Scraped)

Per hotel returned with price, rating, photo, and policies. Includes base search data only — enable the add-on for room details.

• Hotel details enriched (add-on) (booking-hotel-details)

Each Booking.com review returned

• Per monitor run (monitor-run-completed)
• Per new review (new-lot-detected)
• Per alert (alert-delivered)

Charged for each review extracted

• Run started (start)

Per hotel returned (identity, rating, price and availability).

• Prices & availability (prices)
• Review (review)
• Calendar day (calendar_day)

One Booking.com property priced for your dates and guests: its lowest stay price, flags, rating and location (row keys hotel_id, name, url, stars, review_score, review_count, address, latitude, longitude, distance_from_center, price_total, price_nightly, currency, taxes_fees_excluded, free_cancellation, no_prepayment, breakfast_included, room_name): $4 per 1,000 hotels. Not charged: sold-out or unpriced properties (delivered free with Booking's alternative dates), properties maxPrice or minStars remove, a property reached twice in one run, destinations or names that match nothing, status rows, bad input. No start fee; proxy and compute are included in the event price. The run stops at the maximum cost per run you set when starting it (Apify run option maxTotalChargeUsd), never above it.

• Room rate row (room)

Each flight option delivered to the dataset.

• Search (search)
• Browser search (browser-search)
• Booking options (booking-options)
• Return flights (return-flights)
• Price graph day (price-graph-day)
• Explore destination (explore-destination)

Single result in the default dataset.

• Hotel date (hotel-date-scraped)

Charged once per result collected.

• Price breakdown (price-breakdown)
• Coordinates and location details (geo-location)
• Hotel details (hotel-details)
• Host contact (host-contact)

One result row — itinerary, calendar date, destination or search summary. Error rows and empty results are always free. No run fee, no search fee, no proxy fee.

One Booking.com hotel review with score, positive/negative text, reviewer nationality, traveler type, room type, nights, language, and hotel response.

Single result in the default dataset.

• Detailed hotel scraped (details)

Charged for each hotel returned, with its overall guest rating, review count, star rating, address and coordinates.

One guest review row from Booking.com. Error rows and empty results are always free. No fee per run, per hotel or per page.

Charged per successfully scraped result or processed item.

• Hotel Details (hotel-details)
• Availability calendar (availability-calendar)
• Reviews (reviews)

One priced stay for one of your properties - a single check-in date, length of stay and occupancy. Sold-out dates are included, because an empty date is a rate signal too.

• Competitor rate row (compset-rate-row)

Event description unavailable.

Charged once per hotel row pushed to the dataset.

• Actor start (actor-start)

Single result in the default dataset.

• Full hotel detail (add-on). (detail-result)

Any review row or reputation profile row is saved to the dataset

• Property reputation profile (property-review-profile)

Single result in the default dataset.

• Browser start (browser_start)

Charged for each Booking.com hotel photo row saved to the dataset.

• Run started (start)

Per hotel row returned by Hotel Search or Hotel Search by Coordinates.

• Review Result (review-result)
• Forensics Bundle (forensics-bundle-result)
• Hotel Detail (hotel-detail-result)
• Calendar Row (calendar-row-result)

One property from Booking.com with its name, total price for the dates searched, rating, review count, stars, address, coordinates, photo and link. A search that could not be read is never charged, and neither is a search Booking lists nothing for.

• Review returned (review)

Per Hotel

• Reviews (review-scraped)

One Booking.com guest review returned in the default dataset.

Charged per successfully scraped result or processed item.

• Hotel Details (hotel-details)
• Availability calendar (availability-calendar)
• Reviews (reviews)

One guest review of a Booking.com hotel: 1-10 score (and out of 5), title, liked and disliked text, language, review and stay dates, nights, room, traveller type, reviewer name and country, helpful votes, photos and the property's reply (row keys rating, rating_5, title, positives, negatives, text, language, review_date, check_in, check_out, nights, room_type, traveler_type, reviewer_name, reviewer_country, helpful_votes, photos, response): $5 per 1,000 reviews. Not charged: hotel rows (category ratings, review count), status rows, reviews removed by maxRating, sinceDate or requireText, reviews Booking's language, traveller-type and keyword filters skip (never fetched), a hotel given twice, hotels with no reviews, names or URLs that match nothing, bad input. No start fee; proxy and compute are included in the event price. About 4 reviews in 10 are score-only. The run stops at the maximum cost per run you set when starting it (Apify run option maxTotalChargeUsd), never above it.

Charged once per flight pushed to the dataset.

One hotel for one check-in date (only hotels that pass your filters).

• Prices from all booking sites (hotel-prices)

Charged only for a delivered dataset row or completed audit row. Blocked, empty, failed, or no-match source checks are handled in logs/notices and must not create customer-charge rows.

One Booking.com hotel occupancy row pushed to the dataset (availability calendar metrics, occupancy windows, and lead rooms).