Booking Engine URL

Flip.to can pass many variables to your booking engine through URL parameters that you define. Set up your Booking engine URL template in Platform -> Mission Control -> Booking. There are two URLs that can be set up—one is for booking a stay at an accommodation, the other is for booking a stay that includes flight packages.

In addition, depending on the features you use, some areas of your platform will allow you to set a different booking engine URL template to override the original settings in Mission Control.

Example URL using tokens

https://your.bookingengine.com/page.html?hotel=12345&aDate={start-date,format=MM/dd/yyyy}&dDate={end-date,format=MM/dd/yyyy}&rooms={rooms,fallback=1}&adults={adults}&child={children,fallback=0}&pc={promo-code}&airport={traveler-airport-code}

Token	Description
{product-booking-engine-code}	The code that identifies your product. Use only if your platform has been set up with multiple accommodation/destination types and each one is using a unique booking engine code.
{property-booking-engine-code}	The code that identifies your property in your booking engine. Use only if your platform has been mapped with multiple properties and each one is using a unique booking engine code.
{fallback-booking-engine-code}	Optional fallback for the property booking engine code. Use only if there is a possibility that a property code might be passed in that is invalid or not recognized by the platform.
{start-date,format=MM/dd/yyyy}	The arrival date requested for the reservation. Format the date using components and separators that your booking engine supports. Components yy – two-digit year, ie 24 yyyy – four-digit year, ie 2024 M – one-digit for any month below 10, ie 3 MM – two-digit month, ie 03 MMM – three-letter month, ie Sep MMMM – full name of month, ie September d – one-digit for any day below 10, ie 5 dd – two-digit day, ie 05 Separators / – slash . – period - – dash
{end-date,format=MM/dd/yyyy}	The departure date requested for the reservation. Refer to arrival date for specifics.
{nights}	The number of nights requested for the reservation.
{rooms}	The number of rooms requested for the reservation. Supports fallback as follows: {rooms,fallback=1}
{adults}	The number of adults who are part of the reservation.
{children}	The number of children who are part of the reservation. Supports fallback as follows: {children,fallback=0}
{child-age}	The age of any children. Supports formatting as follows: {child-age, format=0-onlap, arrayFormat=repeated} Use format to declare the lap child preference as part of the child age parameter. "0" represents the numerical value in the custom string, which can be configured in various ways ie "0-onlap", "lapchild-0", "age-0-onlap". The platform will automatically insert the custom string to any age under 2. Use arrayFormat to define how to handle multiple child ages. The following values are supported: commaDelimited repeated brackets Examples If token is set to &ages={child-age, arrayFormat=commaDelimited} the output would be &ages=1,2 If token is set to &ages={child-age, arrayFormat=repeated} the output would be &ages=1&ages=2 If token is set to &ages={child-age, arrayFormat=brackets} the output would be ?ages[]=1&ages[]=2
{promo-code}	The promo code used for the reservation.
{short-code}	A short code used when handling unusual booking link URLs.
{language-code}	The user's preferred language. Supports formatting as follows: If lowercase format is required, use {language-code,format=xx} If uppercase format is required, use {language-code,format=XX} If the language code needs to be location-specific, use {language-code,format=xx-XX} and adjust the lowercase/uppercase format as needed For reservHotel booking engine, use {language-code,format=reservhotel}
{traveler-airport-code}	The airport that the user will be flying from.