Skip to content
English
  • There are no suggestions because the search field is empty.

Subroom import when onboarding content from Booking.com

NextPax imports your subroom structure from Booking.com, but the subroom details have to be sent separately.

When a property is first created on Booking.com — with its photos, amenities and other content maintained there — and is then onboarded to NextPax by fetching that Booking.com property content, NextPax imports the property's subroom structure. It does not import the subroom details.

In practice this means the subrooms themselves are brought across, but the granular detail describing each subroom — for example the individual items such as bed types and their capacities (a double bed that sleeps two, and so on) — is not populated from the Booking.com content. Those details must be supplied to NextPax explicitly after the content import, through the property's subroom content endpoint, before they can be distributed onward.

Because of this, a property onboarded from Booking.com content should not be assumed to have complete subroom information automatically. After the content import, verify the imported subrooms through the content API and add any missing detail (bed and other item types, counts and capacities) manually. API reference: [link to insert].

This behaviour applies to content sourced from Booking.com and should not be generalised to other channels or PMS imports, which may populate subroom data differently.