Prebook

Compare with Confirm before BookCopy Anchor Link

Prebook re-validates the offer with the supplier. Whether that is a live or a cached rate depends on the supplier. Docs Before you call Book, compare the Prebook offer with what the guest accepted at Confirm, and stop if anything changed.

function assertSameOffer(confirm: any, prebook: any) {
  const a = confirm.accommodation.combination;
  const b = prebook.accommodation.combination;
  const changed =
    (prebook.warnings?.length ?? 0) > 0 ||
    a.price.amount !== b.price.amount ||
    a.price.currency !== b.price.currency ||
    a.mealPlan.id !== b.mealPlan.id ||
    JSON.stringify(a.cancellationPolicies) !== JSON.stringify(b.cancellationPolicies);
  if (changed) throw new OfferChanged(a, b, prebook.warnings); // show it, ask the guest again
}

Same rooms, same orderCopy Anchor Link

• distributions must repeat the Quote's rooms in the same order, with the same number of people in each. Reordering rooms after the Quote, for example in your UI, triggers "order changed" errors. Docs
• The first person of the first room is the contact person. The first person of each other room is its room holder. Put the adult with an email address and phone number first. See Confirm.
• In the example, roomHolders: ["FIRST_NAME", "EMAIL"] applies to Marta. Everyone else follows otherPersons (FIRST_NAME, LAST_NAME, TITLE), which is why the child Leo also carries a courtesyTitle.

Ages at the end of the stayCopy Anchor Link

• requestedAge is the age at the end of the stay. A child who turns 6 during the stay is 6. Docs
• It must equal the age you sent in the Quote. That is why the Quote should also carry each guest's age at checkout. Docs
• requestedAge is always mandatory, even when requiredField doesn't list it. Docs
• If you send birthDate, it must be consistent with requestedAge. Docs

Latin namesCopy Anchor Link

name and lastName must match ^[\p{IsLatin} .'-]+$: Latin letters, spaces, full stops, apostrophes and hyphens only. Arabic, Cyrillic, Greek and CJK names fail. Transliterate them before Prebook, and keep the original script in your own records. Spec

Pre-validate every guest with the spec's patterns so the guest can fix their input before you call Prebook:

const LATIN_NAME = /^[\p{Script=Latin} .'-]+$/u;            // spec: ^[\p{IsLatin} .'-]+$
const PHONE = /^[0-9]{1,15}$/;                              // digits only, max 15
const PHONE_CC = /^\+[0-9]{1,3}$/;                          // "+34", never "0034"
const DOCUMENT = /^[A-Za-z0-9]+(?:-[A-Za-z0-9]+){0,2}$/;    // max 20 characters

export function guestErrors(p: Person): string[] {
  const e: string[] = [];
  if (p.name && !LATIN_NAME.test(p.name)) e.push('name: Latin letters only, transliterate first');
  if (p.lastName && !LATIN_NAME.test(p.lastName)) e.push('lastName: Latin letters only');
  if (p.phone && !PHONE.test(p.phone)) e.push('phone: digits only, max 15');
  if (p.phoneCountryCode && !PHONE_CC.test(p.phoneCountryCode)) e.push('phoneCountryCode: + and 1 to 3 digits');
  if (p.documentNumber && (p.documentNumber.length > 20 || !DOCUMENT.test(p.documentNumber)))
    e.push('documentNumber: letters and digits, at most two hyphens, max 20');
  if (p.documentType && !p.documentNumber) e.push('documentType sent without documentNumber');
  return e;
}

Phone numbers are validated with Google's libphonenumber (com.google.i18n.phonenumbers). Use the same library on your side. Docs

person or personsCopy Anchor Link

The docs and Postman send distributions[].persons Docs, while the original OpenAPI definition names the array person. Prebook accepts both. Tested

• Send persons, the recommended name. Confirmed
• Responses use person. Tested When parsing, accept both person and persons, and both birthDate and birthdate, because some documentation samples use persons and birthdate. Docs

const guests = (d: any) => d.person ?? d.persons ?? [];
const birthDate = (p: any) => p.birthDate ?? p.birthdate;

Common validation errorsCopy Anchor Link

Errors the API returns on guest data: Docs

More in the FAQ.

GotchasCopy Anchor Link

• Special requests are free text only, in commentToAccommodation. Bedding types cannot be sent. Docs
• Guest names per room are received, but only mandatory data is forwarded to suppliers. Docs
• The booked service later calls the comment commentsToAccommodation (plural). Map both when you read bookings. Spec
• We recommend treating Prebook as non-idempotent and never retrying it automatically. Unverified
• Payloads carry names, emails, phone numbers and documents. Store only what you need, and redact personal data before logs and analytics.

RelatedCopy Anchor Link

• Book, the next step
• Confirm
• Rooms and guests
• FAQ
• The booking flow