Skip to main content
Getting your guest count right before you search is important — OpenBookings uses it both to filter out rooms that don’t fit your party and to calculate any extra-guest surcharges that apply when you’re above a room’s base occupancy. This guide explains how the guest selector works, what the constraints are, and how guest numbers feed into pricing.

​
Using the guest selector

Click the guests field on the search panel to open the Guest Selector. It exposes three independent counters: Use the + and − buttons to adjust each value. The selector starts at 2 adults, 0 children, 1 room by default.
Adults and children are counted separately because rooms have distinct max_adults and max_children limits. A room that sleeps 4 adults may only accept 1 child — or none at all. The API enforces both limits independently.

​
How guest count affects room availability

When you run a search, the API only returns rooms where both of the following are true:
  • max_adults ≥ your adults count
  • max_children ≥ your children count
Rooms that fail either condition are excluded entirely — they won’t appear in results, even at a higher price.
1

Set your correct guest count before searching

Enter the exact number of adults and children in your party. If you under-count to see more options, the rooms shown may not legally or physically accommodate your full group.
2

Adjust the room count if your group needs multiple rooms

If you need 2 rooms for a family, set Rooms to 2. The API filters rooms so that at least rooms units of the qualifying type are available at that property.
The room count you set must not exceed the number of qualifying rooms actually available at a hotel. If you request 3 rooms but only 2 fit your guest configuration, that property won’t appear in results.
3

Run the search and review availability

The results show one room card per hotel — the cheapest room that fits your guest count. If a hotel offers multiple room types, you’ll only see the most affordable qualifying option.

​
How guest count affects pricing

Beyond filtering, your guest count directly influences the price you pay through the extra-guest surcharge modifier.

​
Base occupancy and extra guests

Every room has a base_occupancy — the number of guests the base nightly rate is designed for. When the total number of guests (adults + children) exceeds base_occupancy, an extra-guest surcharge applies for each additional person.
For example, if a room has base_occupancy: 1 and you search for adults: 2, children: 0:
One extra guest triggers the surcharge.

​
Surcharge calculation

The surcharge can be configured as a flat amount or a percentage of the base nightly rate: The surcharge is applied night by night, across every night of the stay.

​
Concrete examples

Room: base_occupancy: 2, base price €100/nightSearch: 2 adults, 0 children, 2-night stay
No extra-guest modifier fires. Total = €200.
Room: base_occupancy: 1, base price €100/nightModifier: type: extra_guest, adjustment_type: flat, adjustment_value: 25Search: 2 adults, 0 children, 2-night stay
Room: base_occupancy: 1, base price €100/nightModifier: type: extra_guest, adjustment_type: percent, adjustment_value: 15Search: 3 adults, 0 children, 3-night stay
Room: base_occupancy: 2, base price €80/nightModifier: type: extra_guest, adjustment_type: flat, adjustment_value: 20Search: 2 adults, 1 child, 1-night stay
Children count toward the total guest number when calculating extra-guest surcharges.
The total_price in every search result already includes any extra-guest surcharge for your party size. You’ll also see "extra_guest" listed in the applied_modifiers array on that result whenever the surcharge fired.

​
Quick reference: guest constraints

If you’re building on top of the API, keep in mind that max_adults and max_children control eligibility, while base_occupancy only controls pricing. A room can appear in results even when guests exceed base_occupancy — it will just cost more.