We love simple and this is what is being delivered on APITUDE for activities. Each client has a different booking funnel and different needs and is our aim to cover them all and exceed expectations with our new API.
This is why we have thought about different booking funnels so that we can provide you some initial thoughts and ideas as well as link those to APITUDE for activities.
In this example, the flow could be:
Another example, with two steps request would be:
Even though it is simple, this could be simpler. Why? Because there are two calls, that considering the implementation of other solutions, won’t be required. These are the search and the download voucher.
The confirmation is a required call. By executing a confirmation the booking will be stored in Hotelbeds system and the customer will be provided, in the response (rate keys, date, time, languages, guidelines for the client to enjoy the service booked, etc), with all relevant information required for a voucher to be created by the client.
Another option is a booking funnel in which there is a payment to collect money from the end client. In this case, it is relevant the use of two calls:
instead of the confirm call. The reason is that you will be holding the allotment or tickets until the confirmation has gone through correctly and the reconfirming. In the event of using only that the confirm call, you will be already confirming the booking regardless of the payment being successful or not. The following diagram summarizes this:
The difference between the previous example and this one is the use of two calls rather than the confirmation call. In this example:
Preconfirm: The booking is pre-confirmed and the allotment is locked.
Payment Platform: Although this step is NOT PROVIDED BY APITUDE for Activities