An illustrative view of how accommodation, room or offer,…
.
Data Marketplace · Property & travel
Compare Booking.com accommodation offers by destination, dates, occupancy, currency, property context, price, and availability.
.
{
"property_id": "illustrative-hotel-7",
"property_name": "Example Central Hotel",
"destination": {
"city": "Lisbon",
"country": "PT"
},
"stay": {
"check_in": "2026-09-14",
"check_out": "2026-09-16",
"guests": 2
},
"price": 248,
"currency": "E…Schema and fields
Start with accommodation, room or offer, search context. Source identity, collection time, and field meaning stay connected so records can move into analysis without losing their context.
property_id stringSource property identity
property_name stringDisplayed accommodation name
destination objectSearch and location context
stay objectCheck-in, check-out, and occupancy
price decimalDisplayed offer value
currency stringDisplayed currency
availability stringObserved availability state
captured_at timestampCollection time
Records in this collection
Explore the Booking.com on-demand API
Accommodation
Room or offer
Search context
Availability observation
Rating summary
Freshness and delivery
Refresh the same destination, dates, occupancy, and market context when offer and availability comparisons must remain comparable.
Snapshot Start from a dated baseline Selected scope and collection window
Refresh Receive recurring updates Cadence and change behavior
Format Use JSON, CSV, or Parquet Schema, partitioning, and manifest
Validation Run repeatable checks Counts, fields, missing states, and version
Booking.com applications
Use source-linked, time-stamped records for rate and availability research, plus accommodation market mapping. Each application starts from the same documented fields and collection context.
01
Compare displayed offers for controlled dates, occupancy, currency, and destination context.
02
Build property and attribute views for selected destinations and property categories.
03
Follow displayed price and availability changes for consistent destination, stay, and occupancy inputs.
From sample to production
Start with representative rows, run the joins and calculations that matter, and shape delivery around the system that will consume the data.
01
Select the entities, markets, fields, dates, and business output the collection should support.
02
Check identifiers, fields, joins, missing states, and source context with your own queries or models.
03
Choose the snapshot or recurring schedule, file format, partitions, manifest, and destination.
Booking.com dataset FAQ
Compare Booking.com accommodation offers by destination, dates, occupancy, currency, property context, price, and availability. Core records include accommodation, room or offer, search context, availability observation, rating summary.
Common applications include rate and availability research, accommodation market mapping, offer change monitoring. Start with the fields and time window required by the business output.
Refresh the same destination, dates, occupancy, and market context when offer and availability comparisons must remain comparable.
Use the on-demand API when your application chooses individual requests and timing. Choose this dataset for a prepared bulk snapshot or recurring file delivery.
Continue the data journey
Compare the adjacent dataset, open the source API, or continue into the relevant data, industry, and solution pages.
Start with real records
Tell us which accommodation and room or offer data you need, plus the markets, fields, dates, and destination. We will map the collection to that requirement.