null

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2

The requirements for the onsite booking require also all steps that are required for redirection, with some additional work needed. Please also verify with your account manager that your are suitable for the onsite booking integration. If you don’t know who is your account manager please contact: partnersupport@holidu.com

In order to use the onsite booking you need to implement two endpoints, the availability endpoint and the booking endpoint. We have high requirements on the data quality and on the data accuracy. You also need to have a high standard in your customer service so we are sure, the booking of the customer is handled accurate and in a decent amount of time.  

  1. You have to update the prices and availability as soon as it changes on your site (e.g. a booking is made), since it is the only price the user sees during his booking process.

  2. You need to make sure that the booking we send you reaches you and is handled within the next 24h. That means at least a confirmation is send to the customer, an automatic confirmation is preferred.

  3. You need to handle the payment with the customer and make sure he is informed about the next steps at all time.


All information about the data we need and the endpoints you can find here


  1. Send data update instantly

In order to display correct data to the user and to avoid that he books a property which is not available anymore, you’ll need to send updated rates and availabilities as soon as there is a change on your side.


Whenever you have a booking on your side, you need to send us the updated availabilities of the concerned property.

Whenever there is a change in your prices, you need to send us the updated rates of the concerned properties.


  1. Additional data needed

We’ll also need you to push us some additional information :


  • All mandatory and optional extra costs
  • Send the properties that should be bookable directly on Holidu as "isBookableOnHolidu": true, in the apartments endpoint


The following needs to be sent only if it is different per apartment. If it’s the same for all properties per domain, you should have given us the information already in the initial questionnaire:


  • Your terms and conditions (in the languages used on domain you want to go live on)
  • Your cancellation policies
  • The payment methods you accept
  • The payment schedule (please note that the percentages calculated are based on the nightly prices without any additional extra cost. For extra costs you should always provide us the payment time when sending the extra cost.)


Send cancellation policy

Below you can find an example for cancellation policy. Please consider that the cancellation policy line which is closest to the check-in date needs to be sent with "daysBeforeArrival": 0,


{

 "isServiceFeeRefunded": true,

 "cancellationPoliciesPerDate": [

   {

     "daysBeforeArrival": 20,

     "cancellationFee": {

       "feeType": "PERCENTAGE",

       "amount": 0.9,

       "currency": "USD",

       "maxAmount": null,

       "minAmount": 100

     }

   },

{

     "daysBeforeArrival": 0, //daysBeforeArrival must be 0 for the cancellation policy line which is closest to the check-in date. In this example, it means this condition applies to days 0 to 19 before check-in.

     "cancellationFee": {

       "feeType": "PERCENTAGE",

       "amount": 0.1,

       "currency": "USD",

       "maxAmount": null,

       "minAmount": 100

     }

   }

 ]

}




  1. Create availability and booking endpoints


We need you to build two endpoints on your side:



For security measures we recommend you to whitelist our IPs so that we can only do requests to you from the following IPs:

  • 54.77.51.111
  • 34.249.124.33
  • 212.114.208.106


  1. Booking response

Please note that it is your responsibility to ensure that your servers are up and running and that the booking notification from Holidu is processed by your system.


When sending a booking response back to Holidu, status response 200 should be used for successful bookings. If a booking fails on your end, then you should not respond with status 200.


However, please note that regardless of the booking response you send to Holidu, Holidu treats all bookings as confirmed. Holidu uses the booking response for logging and monitoring purposes only. If we receive status responses other than 200, Holidu will investigate and react on a case by case basis.

  • No labels