Learn how to interpret child age restrictions, child rates, free stays, and cot and extra-bed policies in the Demand API v3.2.
Properties can define rules that affect whether children may stay and how their stay is priced.
Use the Demand API to:
- Check property age restrictions.
- Retrieve child-rate information for available products.
- Identify age ranges where children stay free.
- Retrieve room-level cot and extra-bed limits and related age and pricing policies.
Children are guests aged 0–17. Include each child’s actual age when searching for accommodation so the API can return relevant availability and pricing.
Child-related availability information and static room limits serve different purposes.
- /accommodations/availability returns information for products available for the requested guest group.
- Its
maximum_occupancy.childrenentries describe child age bands and the maximum number of children covered by each entry. - The
free_stayfield provides pricing information.
- Its
- /accommodations/details returns static room information, including numeric adult and child occupancy limits.
Use both responses when assessing a room and product for a guest group.
| Endpoint | Use it to... |
|---|---|
| /accommodations/search | Search for accommodations using the guest group, including the ages of all children. |
| /accommodations/availability | Retrieve available products and prices for the requested guest group, including applicable child age bands and free-stay information. |
| /accommodations/details | Retrieve property and room information, including minimum guest age, room occupancy limits, and cot and extra-bed policies. Request the relevant extras to return room or policy data. |
See the v3.2 Occupancy and allocation guide for details.
When calling /accommodations/search or /accommodations/availability, include the complete guest group.
Use:
guests.number_of_adults— Total number of adults.guests.children— Ages of all children.guests.number_of_rooms— Number of rooms required.guests.allocation— Requested distribution of adults and children across rooms, when applicable.
For example:
{
"guests": {
"number_of_adults": 2,
"children": [2, 10],
"number_of_rooms": 1
}
}Keep each child’s actual age throughout the search and booking flow.
Do not convert children to adults to obtain a different price or make a guest allocation fit. See the Occupancy & allocation guide for information about allocating guests across rooms.
To retrieve property age policies, request extras: ["policies"] from /accommodations/details.
The policies.minimum_guest_age field defines the minimum age, inclusive, for staying at the property.
For example:
{
"policies": {
"minimum_guest_age": 6
}
}In this example, guests younger than 6 are not allowed to stay.
Interpret minimum_guest_age as follows:
| Value | Meaning |
|---|---|
0 | Guests of any age are allowed. |
1–17 | Guests younger than the specified age are not allowed. |
18 or higher | Children aged 0–17 are not allowed. |
A property with minimum_guest_age set to 18 or higher does not allow children aged 0–17.
Do not use maximum_occupancy.children from /accommodations/availability to determine whether a property is adults-only.
In particular, maximum_occupancy.children: null is not a reliable indicator that children are prohibited.
minimum_guest_age is different from minimum_checkin_age.
minimum_guest_agedefines the minimum age of guests who may stay at the property.minimum_checkin_agedefines the minimum age required to check in.
For practical examples covering adults-only properties and other minimum guest ages, see the Occupancy and allocation use cases.
Child rates are pricing rules that apply to children based on criteria such as their age and the product configuration.
Call /accommodations/availability with the complete guest group to retrieve current products and prices.
An available product can return child-rate information in maximum_occupancy.children:
{
"maximum_occupancy": {
"adults": 2,
"children": [
{
"total": 1,
"from_age": 0,
"to_age": 5,
"free_stay": true
},
{
"total": 1,
"from_age": 6,
"to_age": 12,
"free_stay": false
}
],
"total": 4
}
}Each children entry describes an age band:
Field | Description |
|---|---|
from_age | Youngest child age covered by the entry. |
to_age | Oldest child age to which the child-rate rule applies. |
total | Maximum number of children to which the child-rate rule applies. |
free_stay | Whether children covered by the rule stay free of charge. If false, their cost is already included in the returned product price. |
Both from_age and to_age are inclusive.
The availability response is tailored to the requested guest group.
The age bands in /accommodations/availability describes child-rate information for the product, and do not replace the static room occupancy limits returned by /accommodations/details.
Use /accommodations/details to check the room occupancy limits:
- Request
extras: ["rooms"]to retrieve room information. - Check the
rooms[].maximum_occupancyin the response to see the room’s static limits.
The v3.2 room-level maximum_occupancy contains numeric adults and children limits, but it does not contain child age bands.
Use the room limits together with the selected product’s availability information.
Check the selected product and guest allocation with /orders/preview before creating the order.
An available product can return:
{
"maximum_occupancy": {
"adults": 2,
"children": null,
"total": 4
}
}children: null means no age-specific child-rate information is returned for the product. Children are priced at adult rates.
This does not mean children are prohibited.
Call /accommodations/details and check the policies.minimum_guest_age for property age restrictions and use the room occupancy limits to assess the room’s capacity.
free_stay indicates whether children covered by a child-rate rule stay free of charge.
For example:
{
"maximum_occupancy": {
"children": [
{
"total": 1,
"from_age": 0,
"to_age": 5,
"free_stay": true
}
]
}
}In this example:
- The rule applies to children aged 0–5, inclusive.
- Up to one child can use the rule.
free_stay: trueindicates that a child covered by the rule stays free of charge.
The returned product price already accounts for the applicable child pricing. Do not subtract the child's price or recalculate the product total yourself.
free_stay describes pricing; it does not mean the child is excluded from the room’s occupancy limits. Check /accommodations/details when you need to determine whether the child can be accommodated.
Cots and extra beds have separate policy and room-level information.
Use /accommodations/details to retrieve:
- Property-level age and pricing rules through
policies.cots_and_extra_beds. - Room-level limits through
rooms[].cots_and_extra_beds.
Include extras: ["rooms"] and extras: ["policies"] in the request:
{
"accommodations": [27635],
"extras": [
"policies",
"rooms"
]
}policies.cots_and_extra_beds contains age-related pricing rules for cots and extra beds.
For example:
{
"policies": {
"cots_and_extra_beds": [
{
"age": {
"from": 0,
"to": 2
},
"mode": "per_night",
"price": 0,
"type": "cot"
}
]
}
}Use the fields as follows:
| Field | Description |
|---|---|
age.from | Youngest guest age to which the rule applies. The age interval is inclusive. |
age.to | Oldest guest age to which the rule applies. The age interval is inclusive. The schema uses 18 or null to represent adults. |
mode | How the price is applied per cot or extra bed, such as per_night or per_stay. |
price | Price of the cot or extra bed. A value of 0 indicates that it is free of charge. |
type | Whether the rule applies to a cot or an extra_bed. |
rooms[].cots_and_extra_beds describes the number of cots and extra beds that can be added to a particular room.
For example:
{
"rooms": [
{
"id": "2763504",
"cots_and_extra_beds": {
"are_allowed_together": false,
"maximum_number_of_cots": 1,
"maximum_number_of_extra_beds": 0
}
}
]
}Use:
maximum_number_of_cots— Maximum number of cots that can be added to the room.maximum_number_of_extra_beds— Maximum number of extra beds that can be added to the room.are_allowed_together— Whether cots and extra beds can be placed in the room at the same time, up to their respective limits.
Use policies.cots_and_extra_beds and rooms[].cots_and_extra_beds together.
The policy describes the applicable age and pricing rules, while the room information describes how many cots or extra beds can be added.
Cot and extra-bed information is separate from the room's standard occupancy configuration.
When determining whether a guest group can be accommodated:
- Check the room's
maximum_occupancy. - Check the applicable cot or extra-bed policy.
- Check the room-level cot and extra-bed limits.
- Validate the selected product and exact guest allocation using /orders/preview before creating the order.
For worked examples, see Handle cots and extra beds.
Use the child-policy information returned by the API to provide travellers with relevant information about their stay such as:
- Child age bands and whether children in those bands stay free.
- Cot and extra-bed availability and applicable charges.
- The property’s minimum guest age or other relevant age restrictions.
Always display the product price returned by the API. Child-rate and free-stay rules are already reflected in the returned price.
Do not infer or display that children are charged as adults solely because maximum_occupancy.children is null.
Do not calculate child prices independently from the product price returned by the API.
When handling a search that includes children:
- Send each child's actual age in /accommodations/search.
- Check
minimum_guest_agefrom /accommodations/details when property age restrictions are relevant to your integration. - Call /accommodations/availability for the selected accommodation using the complete guest group.
- Use
maximum_occupancy.childrento interpret the applicable child-rate information for each product. - Use
free_stayto identify child-rate bands where children stay free of charge. - When you need to determine whether the guest group fits a particular room, use the room occupancy information from /accommodations/details.
- Retrieve
policies.cots_and_extra_bedsandrooms[].cots_and_extra_bedswhen cot or extra-bed information is relevant. - Use /orders/preview to validate the exact product and guest allocation before creating the order.
- Always provide children's actual ages in search, availability and preview requests.
- Keep child pricing rules separate from room occupancy rules.
- Do not use
maximum_occupancy.childrenfrom /accommodations/availability alone to determine whether children fit the room. - Do not interpret
children: nullas confirmation that children are prohibited or should be treated as adults. - Use
minimum_guest_ageto determine property-level age restrictions. - Use the product prices returned by the API rather than calculating child prices yourself.
- Treat cot and extra-bed policies separately from standard room occupancy.
- Validate the final product and guest allocation using /orders/preview.
- See the Occupancy & allocation guide for guest allocation, room occupancy rules,
recommendation, andoccupancy_mismatch. - See the Occupancy and allocation use cases for worked family-booking examples covering versions 3.2.
- Refer to the Accommodation search guide for instructions and best practices when using /accommodations/search and /accommodations/availability.