Tourpaq Web Booking - Technical documentation
The Tourpaq Web Booking is a component of Tourpaq booking platform which allows the customers themselves to book travel packages, pay various amounts of their choice, print ticket or manage the products they have chosen for the holiday. The Web Booking application is using different themes for each Brand/Agency that uses it and also small customizable differences in behavior. One of the most important pages, and the entry point in the Web Booking application, is the DoBooking.aspx page. This is the page that receives the needed details by query string either by desktop browsers or by mobile applications.
The detailed description of each of the required parameters is found bellow. An important note is to be made on the validity of the entire group of parameters. In case a test made to check the integrity of the parameters fails, then the booking attempt is denied, a message is listed to the customer and an email with details is sent to the webmaster.
Here is an example of web booking entry point URL. The domain address is usually represented by "[agencyBrandName].webbooking.tourpaq.com". Also a staging test environment should exist for each Web Booking implementation at “staging.[agencyBrandName].webbooking.tourpaq.com” with the comment that the staging database is usually an older (and cleaned) copy of the live database, but no longer than 2-3 weeks old.
Parameter description
https://primotours.webbooking.tourpaq.com/DoBooking.aspx ?pltaID=84042&p=1&rno=3&pt=2&a=6&c=1&aa=14&ca=3&f=1&fd=12&ft=1
pltaID
“Price list transport allotment id” - Provides most of the needed information: departure date, duration, return, hotel room, base price etc.
Only positive integer values of PriceListTransportAllotmentIDs belonging to the current agency. Fails the integrity test if the departure is in the past or sooner than minimum limit set on agency, requested price is set to zero and other possible reasons. Please see second table for details on such scenarios.
p
“Period” – states the holiday duration
Only integer values within “1,2,3,4, 100, 101” representing the 4 intervals that a price can be defined on plus the one way transport modes - fly out and fly home. If the URL will contain both periods 100 and 101, that means we are dealing with a Custom Trip, with each flight unbound by a particular rule from the other flight. Example of standard intervals: Interval 1 might be 7 days, all the other Intervals 2, 3, 4 can only be multiples of I1 - 14, 21, 28 days.
rno
“Room numbers” – self-explanatory with the observation that the Web Booking can currently book only one type of room per booking. No bookings with 2 different types can be made.
Only integer values greater than 0. Fails if the booking passenger no. is greater than the maximum beds in the rooms or if the minimum beds to be occupied in rooms is lower than the passenger no.
pt
“Price type” – states if the price should be a group price (3), discount (2) or normal price (1)
Only integer values within “1,2,3”
a
“Number of adults”
Positive integers
c
“Number of children”
Only integers (can be 0) – in combination with adults no. determines the passenger total of the booking. Fails if the passenger no does not fall within the maximal or minimal number of beds.
aa
“Adult ages” – accepts values such as “15,17,17”. In the above example’s scenario it will mean that 3 adults will be considered 99 years of age and 3 adults will have the provided ages.
//Optional//. Expects string of integer positive values delimited by comma.
ca
“Children ages” – requires to contain the same number of ages as the “c” parameter states in this case ages will not be set to a default age as in “aa”s case.
Fails if “c” is 0 and “ca” provides values or if “c” is greater than 0 and “ca” does not provide the same number of ages delimited by comma.
db
“Discount bonus code” – states if the booking benefits from a bonus code campaign.
//Optional// - can be string insensitive with minimum 5 chars and maximum 20 chars except 12(which is used for giftcard codes). If not valid, no discount gets applied.
f
“Booking should be financed” – “1” meaning the payment of the booking will be made by a financial society in rates. Not possible if the departure is in the next 21 days from the booking date.
//Optional//. Accepts only values of “0” or “1”.
fd
“Financing duration in months” – each of the agencies has an accepted interval of financing months. For example a value within “0,12,24,36,48,60,72”
//Optional only if// “f” is 0 or not provided. Fails if the value is not inside the accepted interval for the current agency and financing type.
ft
“Financing type” – currently there are 3 types of financing. Example: first 6 months pay nothing and continue paying rates afterwards, fixed rate, dynamic rate etc.
//Optional only if// “f” is 0 or not provided. Fails if value is not “1”, “2”, “3” or “4”
offerNo
“OfferNo” – Representing the OfferHash from [dbo].[CustomerOffer]
Optional parameter
uh
“UserHash” – Representing the encoded userID of the sales agent that sent an offer to the customer
Optional parameter
A more complex scenario of the Web Booking URL is the one with multiple room types such as: https://primotours.webbooking.tourpaq.com/DoBooking.aspx ?pltaID=84042,84572&p=1&rno=3,1&pt=2,1&a=6,2&c=1,1&aa=14&ca=3,7&f=1&fd=12&ft=1\ The above integrity rules still apply, only that most of the parameters need a dual value, or multiple value according to the situation, if the booking should have 3,4 or more room types bought.
As of February 2016, the children distribution in rooms by their age can be obtained precisely in the URL. For this, the children ages need to be split into room iterations as well as all the other multiplied parameters, only that the separator for them must be the pipeline "|". DoBooking.aspx?pltaID=729932,729961&p=1&rno=2,1&pt=2,2&a=4,1&c=1,2&aa=&ca=9|12,5
Doubling is either accepted on ALL parameters (except p-period) or doubling is accepted on NO parameter. URL like this is not supported: //pltaID=1767430&p=1&rno=2&pt=1&a=4&//c=2,2&aa=&ca=4,1|5,0
Please note that the URL parameter structure from Web Booking can be used in Office also as: http://staging-booking.tourpaq.com/BookingEngine/EditBooking/Booking.aspx?pltaID=.....
'' No longer the case with Faster Web Booking. Detailed warning message is presented on the spot.''
Error page interpretation
'' No longer the case with Faster Web Booking. Detailed warning message is presented on the spot.''
In case you do encounter an integrity fail situation, you will be redirected to a page such as http://primotours.webbooking.tourpaq.com/Error.aspx?e=0&salg=0
e
This represents the error type you encounter.The main situations when a booking attempt can be rejected have been split into several major categories.
Values here are set by the system and can be anything from 1, 2, 3 until any current category number we have reached at some point in time.
salg
This parameter was named similar to the one in the presentation site for easy remembering. This was required so the visitors do not see the technical reasons themselves. In order to set this, please copy paste the window url to a new browser window and set this parameter to "1".
Values can be "0" which is set by default and "1" which will provide some more details on the reason why the booking was rejected. Example: //Error: Parameter configuration was incorrect (or requested price is zero) (or the plta is generated for a different agency)
Used parameters: pltaID=202628&p=1&rno=1&pt=2&a=2&c=0&aa=&ca=8&f=0&fd=12&ft=1.// When receiving this, please check each possible scenario described as from the most likely to the least likely one. If settings are right please contact Tourpaq Support with providing these details and any other relevant ones.
Last updated
Was this helpful?