Booking.com Scraper - Hotels, Prices & Reviews (LATAM) avatar

Booking.com Scraper - Hotels, Prices & Reviews (LATAM)

Pricing

from $3.00 / 1,000 accommodation scrapeds

Go to Apify Store
Booking.com Scraper - Hotels, Prices & Reviews (LATAM)

Booking.com Scraper - Hotels, Prices & Reviews (LATAM)

Extract Booking.com hotel and accommodation listings across Latin America: prices, ratings, reviews, room types, amenities and location for BR, MX, AR, CO, CL, PE.

Pricing

from $3.00 / 1,000 accommodation scrapeds

Rating

0.0

(0)

Developer

viralanalyzer

viralanalyzer

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

19 days ago

Last modified

Categories

Share

Booking.com Latin America Scraper 🏨 Hotels, Apartments & Reviews

English | Português


English

Extract comprehensive accommodation and hotel listings from Booking.com across Latin America (Brazil, Mexico, Argentina, Colombia, Chile, Peru, and more) with ease. Capture rates, user ratings, review counts, coordinates, distance to center, and room details.

This Actor uses Pay-Per-Event (PPE) pricing, meaning you only pay for the real data you actually extract — no monthly subscriptions or upfront fees required.

Features

  • 🌎 Latin America Coverage: Optimized for destinations across Central and South America.
  • 🏢 All Accommodation Types: Extracts Hotels, Hostels, Apartments, Resorts, and Guesthouses.
  • 💰 Pay-Per-Event Billing: Only $0.006 per extracted accommodation. Immediate billing, zero free-trial delays.
  • 🛡️ IP Reputation Bypass: Works flawlessly using Apify's default automatic proxy rotation.
  • Rich Structured Data: Extracts ID, name, price, rating, total review count, room type, full address, distance from center, key amenities, and photos.

Input Parameters

FieldTypeDescriptionDefault
urlStringDirect Booking.com search URL. Overrides other filters.""
locationStringCity or destination slug (e.g. Sao Paulo, Cancun, Buenos Aires)."Sao Paulo"
checkinStringCheck-in date in YYYY-MM-DD format. Optional, but never absent from the search — see "Capabilities & Limits".run date + 10 days
checkoutStringCheck-out date in YYYY-MM-DD format. Must be after checkin.run date + 12 days
guestsIntegerNumber of adult guests.2
currencyStringCurrency code for prices (BRL, USD, MXN, ARS, COP)."BRL"
maxListingsIntegerMaximum number of listings to extract.100
proxyConfigurationObjectProxy configuration. Default automatic proxy is highly recommended.{"useApifyProxy": true}

Output Example

{
"id": "3589482",
"name": "Hotel Transamerica Berrini",
"price": 420,
"priceFormatted": "R$ 420",
"currency": "BRL",
"rating": 8.7,
"reviewCount": 2450,
"roomType": "Standard Double Room",
"address": "Itaim Bibi, São Paulo",
"location": "São Paulo",
"distanceFromCenter": "6.8 km from center",
"features": [
"Free WiFi",
"Breakfast included",
"Free cancellation"
],
"images": [
"https://cf.bstatic.com/xdata/images/hotel/max1024x768/3589482.jpg"
],
"imageCount": 1,
"url": "https://www.booking.com/hotel/br/transamerica-berrini.html",
"source": "Booking.com",
"scrapedAt": "2026-05-23T14:56:00.000Z"
}

Use Cases

  • 📊 Market Price Monitoring: Track hotel and apartment room rates for dynamic pricing.
  • 🎯 Tourism Market Research: Extract ratings and review scores to analyze customer satisfaction.
  • 💼 Travel Agency Aggregation: Enrich your booking application with real-time accommodation details.

✅ Capabilities & Limits

Stated up front, so you do not pay a run to find out.

Built here: a page.route hook aborts every image, media and font request before navigation, so the run never downloads a single hotel photo - yet images and imageCount are still fully populated, because they are read from the <img src> attributes in the DOM. You get the image URLs at a fraction of the bandwidth and compute of a normal browser run.

Dates are never empty: if you send no url and no checkin/checkout, the Actor writes dates into the search itself — check-in at run date + 10 days, check-out at run date + 12 days. A fixed 2-night stay on a window that slides forward with the calendar. So the prices you receive are quotes for that window, and the same input launched on 3 March and on 10 March hits two different date ranges and returns two different rate sets. Those two runs are not comparable. Sending only one of the two dates does not pin anything either: the Actor overwrites both. To track a rate over time, set checkin and checkout explicitly, or pass a url that already carries the dates.

Input / featureSupportedNotes
urlDirect search results URL from Booking.com. The Actor fetches it as given: location, checkin, checkout and guests are not applied and no dates are injected. currency still is — selected_currency gets appended when the URL does not already carry it. One trap: the location you send is still copied into the location field of every output row, so a Cancún URL left with the default location labels its rows "Sao Paulo". Example: https://www.booking.com/searchresults.html?ss=Sao+Paulo&dest_type=city&checkin=2026-09-10&checkout=2026-09-12
locationCity or destination in Latin America. Example: 'Sao Paulo', 'Rio de Janeiro', 'Cancun', 'Buenos Aires', 'Cartagena'. Default is 'Sao Paulo'.
checkinYYYY-MM-DD. Empty means run date + 10 days, not a dateless search.
checkoutYYYY-MM-DD, must be after checkin. Empty means run date + 12 days.
guestsNumber of adult guests.
currencyCurrency for prices.
Result volume (maxListings)⚠️Maximum number of accommodation listings to extract. Each search page has ~25 listings.
Proxy⚠️Proxy configuration. Using Apify's default automatic proxy is recommended and works fine for Booking.com.

FAQ

Q: Do I need a residential proxy?
A: No. Unlike heavily locked portals, Booking.com is very stable and works perfectly using Apify's default automatic proxy pool.

Q: How does the Pay-Per-Event model work?
A: You are only charged per listing successfully scraped and saved to your dataset. If a run fails or returns 0 results due to a block, you pay absolutely nothing.


Português

Extraia dados completos de anúncios de hotéis e alojamentos do Booking.com em toda a América Latina (Brasil, México, Argentina, Colômbia, Chile, Peru, entre outros) de forma simples. Capture tarifas, avaliações dos utilizadores, quantidade de comentários, distância ao centro e detalhes dos quartos.

Este Actor utiliza a cobrança Pay-Per-Event (PPE) via API, o que significa que paga apenas pelos dados reais que extrair — sem subscrições mensais ou taxas iniciais.

Funcionalidades

  • 🌎 Cobertura Latam: Otimizado para destinos em toda a América Central e do Sul.
  • 🏢 Todos os Alojamentos: Extrai Hotéis, Hostels, Apartamentos, Resorts e Casas de Hóspedes.
  • 💰 Cobrança Pay-Per-Event: Apenas $0.006 por alojamento extraído. Cobrança imediata e sem períodos de teste gratuitos.
  • 🛡️ Segurança de IP: Funciona perfeitamente usando a rotação automática padrão de proxies da Apify.
  • Dados Ricos e Estruturados: Retorna ID, nome, preço, avaliação, contagem de reviews, tipo de quarto, morada completa, distância ao centro, principais comodidades e imagens.

Parâmetros de Entrada

CampoTipoDescriçãoPadrão
urlStringURL de pesquisa direta do Booking. Ignora os outros filtros.""
locationStringCidade ou destino (ex: Sao Paulo, Cancun, Buenos Aires)."Sao Paulo"
checkinStringData de check-in no formato AAAA-MM-DD. Opcional, mas nunca ausente da busca — ver nota abaixo.dia da execução + 10 dias
checkoutStringData de check-out no formato AAAA-MM-DD. Precisa ser posterior ao checkin.dia da execução + 12 dias
guestsIntegerNúmero de hóspedes adultos.2
currencyStringMoeda de exibição (BRL, USD, MXN, ARS, COP)."BRL"
maxListingsIntegerNúmero máximo de alojamentos a extrair.100
proxyConfigurationObjectConfigurações de proxy. Proxy automático recomendado.{"useApifyProxy": true}

As datas nunca ficam vazias: sem url e sem checkin/checkout, o Actor escreve as datas na busca — check-in no dia da execução + 10 dias, check-out no dia da execução + 12 dias. É uma estadia fixa de 2 noites numa janela que anda junto com o calendário. Os preços retornados são cotações dessa janela: o mesmo input rodado dia 3 e dia 10 consulta intervalos diferentes e devolve tarifas diferentes. Essas duas execuções não são comparáveis. Enviar só uma das datas também não resolve — o Actor sobrescreve as duas. Para acompanhar uma tarifa ao longo do tempo, fixe checkin e checkout, ou passe um url que já contenha as datas.

Casos de Uso

  • 📊 Monitorização de Tarifas: Acompanhe os preços de quartos de hotéis e apartamentos para precificação dinâmica.
  • 🎯 Pesquisa de Mercado: Analise avaliações e comentários para entender a satisfação dos clientes em destinos turísticos.
  • 💼 Agências de Viagens: Enriqueça a sua aplicação ou plataforma com detalhes e preços reais do Booking.com.

💰 Pricing / Preços

This actor uses Pay Per Event (PPE) pricing — no monthly fees:

MetricCost
accommodation-scraped$0.006 per accommodation

Example: Extracting 1,000 accommodations costs $6.00. Runs that return 0 results (e.g. blocked) are not charged.

Este actor usa cobrança Pay Per Event (PPE) — sem mensalidade. Custo: $0.006 por alojamento (accommodation-scraped). Exemplo: 1.000 alojamentos custam $6.00. Execuções com 0 resultados não são cobradas.

Changelog

  • v1.0.0 (2026-05-23): Lançamento oficial do Booking.com Latam Scraper com cobrança imediata PPE e suporte a múltiplos países da América Latina.