Bookings data (cancellation and modification synchronisation)
When a booking is being placed on Holidu, we will send you a booking notification (see Booking notification for more details). Most post-booking operations will then be handled on your side, between the traveller and you, out of synchronization with the initial Holidu booking entry. This is why it is important that you keep notifying us for any change relating to the bookings.
Example of use case 1:
Booking cancellation
User abc@gmail.com has booked on Holidu a trip for next summer to Italy. A few weeks before the trip, user abc@gmail.com is requesting you to cancel his trip. In this case, you should notify Holidu of this cancellation.
Example of use case 2:
Booking modification
User abc@gmail.com has booked on Holidu a trip for next summer to Italy. A few weeks before the trip, user abc@gmail.com is requesting you to delay the trip by 1 week, and to add 2 more adults to the reservation. In this case, you should notify Holidu of this modification (even if the price did not change).
To fulfil this purpose, the HOLIDU API offers three endpoints available to implement automatic update / synchronisation of bookings between Holidu and your own system:
POST /rest/public/integration/bookings → for updating or creating a booking.
This endpoint should be used in the following cases :
A customer has updated his/her booking (changed travel dates, changed number of travellers, added extra_costs, ...). You will need to notify us of these changes.
A customer has cancelled his/her trip, received a voucher, and created a new one with the voucher. You will need to notify us of this new trip.
POST /rest/public/integration/bookings/cancel → for canceling a booking. (This endpoint is required)
This endpoint should be used whenever a booking is cancelled on your end, either by you or by the traveler.
GET /rest/public/integration/bookings/details → for retrieving a booking information of booking.
This endpoint lets you retrieve all details associated to a booking.
When updating or canceling the booking you need to provide us with a bookingId or a holiduBookingId. If you are using bookingId (ID in your system) please make sure that you include a transactionId in your response to our booking notification.
If you are updating bookings for mutual (sub) partners, please note that a partner account name on Holidu is mandatory.
When cancelling a booking you need to provide us with the booking cancellation reason in the request. Please see all the possible values below.
Example requests
Updating a booking.
curl -X POST "https://provider-api.holidu.com/rest/public/integration/bookings" -H "accept: */*" -H "api_key: YOURAPIKEY" -H "Content-Type: application/json" -d "{ \"providerApartmentId\": 123456, \"bookingId\": \"B123456\", \"subId\": \"abc\", \"dateOfBooking\": \"2020-09-18T18:06:13.918Z\", \"arrival\": \"2020-10-20\", \"departure\": \"2020-10-30\", \"commissionablePrice\": { \"amount\": 821.8, \"currency\": \"EUR\" }, \"totalPrice\": { \"amount\": 821.8, \"currency\": \"EUR\" }, \"numberOfGuests\": 2, \"customer\": { \"country\": \"string\", \"email\": \"string\", \"firstName\": \"string\", \"lastName\": \"string\", \"phone\": \"string\" }}"Cancel a Booking
curl -X POST "https://provider-api.holidu.com/rest/public/integration/bookings/cancel?bookingId=providerbookingid123&reason=CUSTOMER_ALTERNATIVE_ELSEWHERE_OTHER" -H "accept: */*" -H "api_key: YOURAPIKEY"You can read more on the endpoints in our API Swagger page.
In case you have any questions, please contact providersupport@holidu.com