One entry per room type with availability on your dates - not the property's whole catalogue, which is usually larger. Occupancy, bed layout, bedrooms, bathrooms, size, photos and child policy. bedCount counts beds, not sleeping places: a bunk counts once and sleeps two, so a "14-Bed Private Room" can report 7. Use maxOccupancy for capacity, and note that is the largest occupancy Booking offers your party rather than the room's own. areas[] says which room each bed is in for apartment-like units (bedroom, living room, each with its own beds, sleeps and en-suite flag), with hasLivingRoom beside bedroomCount; null on ordinary hotel rooms, which publish no layout. areas[] places beds, it does not inventory rooms: two entries of the same type can describe one room (measured against Booking's own room summary, counting them overstates living rooms on 2 of 14 units), which is why hasLivingRoom is a flag and not a count. areas[].beds[] and bedLayouts are the same beds from different angles, so summing across both double-counts - bedCount stays the one number to trust.