Web Hooks/Tracking Parameters/Reporting Scripts
Web Hooks:
WebHooks are a way to tell us to call a script on one of your own web servers whenever a given event occurs and react in any way you want. They can be thought of as push notifications or event listeners.
Once you register a webhook URL with us we will issue a HTTP POST request to the URL specified every time a reservation occurs. The request's POST parameters will contain XML data of the full booking response with all customer, room, and rate information.
If your server is down when we POST to it, don't worry; we'll simply try again until your server confirms to us that it has successfully received the notification.
We will call the URL you provide here every time a reservation is booked. This means that if a guest books 10 rooms, your webhook will be called 10 times.
Timeout: The web hook request will time out after 10 seconds. Your page should simply accept the data for later processing and return immediately with a status code of 200 to indicate success.
If an error is returned or a timeout occurs when sending a webhook, we will retry the same request for 48 hours using an exponential back-off approach. In total 20 attempts will be made to deliver the information.
WebHooks are a way to tell us to call a script on one of your own web servers whenever a given event occurs and react in any way you want. They can be thought of as push notifications or event listeners.
Once you register a webhook URL with us we will issue a HTTP POST request to the URL specified every time a reservation occurs. The request's POST parameters will contain XML data of the full booking response with all customer, room, and rate information.
If your server is down when we POST to it, don't worry; we'll simply try again until your server confirms to us that it has successfully received the notification.
We will call the URL you provide here every time a reservation is booked. This means that if a guest books 10 rooms, your webhook will be called 10 times.
Timeout: The web hook request will time out after 10 seconds. Your page should simply accept the data for later processing and return immediately with a status code of 200 to indicate success.
If an error is returned or a timeout occurs when sending a webhook, we will retry the same request for 48 hours using an exponential back-off approach. In total 20 attempts will be made to deliver the information.
Tracking Parameter:
A Tracking parameter can be placed on a query string for tracking where a query originated.
The CID will report throughout the sale and with both the booking details and commissioning reports.
Example: http://www.reservetravel.com/v6?siteid=64&cid=12345example
A Tracking parameter can be placed on a query string for tracking where a query originated.
The CID will report throughout the sale and with both the booking details and commissioning reports.
Example: http://www.reservetravel.com/v6?siteid=64&cid=12345example
Reporting Scripts:
If you are interested in passing a parameter of some sort that you can then receive a notification from us when a customer books along with some details about the booking:
When you link off, pass a <<&linkId=>> parameter in the url. Whatever you pass we'll pass back to a page of your choosing on the confirmation page. Something like an invisible pixel that loads. We can pass back the following things in a conversion template:
<linkId>
<confirmation>
<paid>
<total>
<property>
<totalUSD>
<currency>
<checkIn>
<checkOut>
<nights>
<rooms>
<adults>
<guestFirstName>
<guestLastName>
<siteId>
<rateCode>
<roomCode>
<rateDescription>
<roomDescription>
Which might look something like:
<img src="https://someUrl/somePage?linkId=<linkId>&confirmation=<confirmation>&paid=<paid>&total=<total>&property=<property>&totalUSD=<totalUSD>¤cy=<currency>&checkIn=<checkIn>&checkOut=<checkOut>&nights=<nights>&rooms=<rooms>&adults=<adults>&guestFirstName=<guestFirstName>&guestLastName=<guestLastName>&siteid=<siteId>&rateCode=<rateCode>&roomCode=<roomCode>&rateDescription=<rateDescription>&roomDescription=<roomDescription>">
If you are interested in passing a parameter of some sort that you can then receive a notification from us when a customer books along with some details about the booking:
When you link off, pass a <<&linkId=>> parameter in the url. Whatever you pass we'll pass back to a page of your choosing on the confirmation page. Something like an invisible pixel that loads. We can pass back the following things in a conversion template:
<linkId>
<confirmation>
<paid>
<total>
<property>
<totalUSD>
<currency>
<checkIn>
<checkOut>
<nights>
<rooms>
<adults>
<guestFirstName>
<guestLastName>
<siteId>
<rateCode>
<roomCode>
<rateDescription>
<roomDescription>
Which might look something like:
<img src="https://someUrl/somePage?linkId=<linkId>&confirmation=<confirmation>&paid=<paid>&total=<total>&property=<property>&totalUSD=<totalUSD>¤cy=<currency>&checkIn=<checkIn>&checkOut=<checkOut>&nights=<nights>&rooms=<rooms>&adults=<adults>&guestFirstName=<guestFirstName>&guestLastName=<guestLastName>&siteid=<siteId>&rateCode=<rateCode>&roomCode=<roomCode>&rateDescription=<rateDescription>&roomDescription=<roomDescription>">