Booking Funnel Alignment

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.

A simple booking funnel

One possible booking funnel could be:


In this example, the flow could be,-

  1.   It is initially starting with search,
  2.   Then detail information being taken of a particular poduct, 
  3.   Then confirmation, 
  4.   And finally a voucher that is downloaded. 

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 Search call, which returns all available products, can be skipped in the event that you already know the product you would like to have details for or that you have implemented the Active Inventory for Activities and Active Content or if you have already applied a cache for available product. 
  • In this case you can jump and go directly to the “detail” call to obtain the price for a specific service along with the days it can be booked and all relevant information required to do the booking.

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.

Download voucher

  • For some particular products vouchers will be already given. 
  • In some products such as Futbol Club Barcelona match tickets, the supplier requires a specific format for the voucher since, otherwise, the final consumer will not be allowed to enjoy the activity, in this case a particular match of the Futbol Club Barcelona. 
  • If a voucher structured is returned in the Confirmation call then it must be used. 
  • The voucher for the booking will be returned in different languages and formats and URLs will be provided for the customer to use. 
  • However, if the voucher URL is not provided then you will be able to create your own voucher.  
  • We are also capable of generating vouchers on your behalf. Please for this contact us and agree with our team before starting the development.

A booking funnel considering the payment

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:

  • Preconfirm
  • Reconfirm

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:

PreconfirmThe booking is pre-confirmed and the allotment is locked. 

    • You will have 30 minutes to complete the booking and reconfirm. 
    • Otherwise the session will expire and the product will not be able to be confirmed with the same preconfirmation done. 
    • You will need to do another preconfirmation before using the reconfirm call.
  • Payment Platform: Although this step is NOT PROVIDED BY APITUDE for Activities

    • The step represents the point where you allow your final customer to pay for the services purchased with the payment method of your choice.


    • When you are done with the payment, you can confirm the booking by using the reconfirm API call. 
    • The response and behavior is the same that the confirm operation.

    A booking of an excursion where a pickup is required to be selected

    We provide two types of products:

    • Tickets = "type": "TICKET"
    • Excursions = "type": "EXCURSION"

    The main difference between each other is that the excursion product has a pickup location where the customer will be picked up to start the sightseeing and also that it has an itinerary associated with it while a Ticket is an entrance to a show, museum or other where the customer will get himself to the venue and it will not be taken.

    "RetrievePickups" for Excursion 

    In the event that a product type excursion has the pickup being returned in the “detail” call, a second call, “RetrievePickups”, must be performed to get the Rate Key needed to confirm a booking.

    This call shall take place after the Detail after which you can decide to use the preconfirmation and reconfirmation or straight go to the confirmation. Take into consideration what was explained before.

    booking excursion

    The product type excursion typically is marked with activity.type = “EXCURSION”.

    The criteria to decide whether to retrieve the pickups or not is: The rateKey parameter is not returned in the “detail” API call, but a RateRetrievePickups is provided and needs to be sent to the “Retrieve Pickups” API call.

    Docs Navigation