Caching Results

Most of us are today looking for alternatives to improve performance and reduce costs by adding cache solutions that contain all required information and speed up the availability process.

We strongly recommend that you look at two solutions that we have in place that allow you to cache most of our product without the need to scan our platform or use calls.

Active Inventory – This solution provides a consolidated list of all products available (in files) that you can download and use offline. With those files you will be able to calculate the a price for a given activity following the same parameters that you use in the API but without calling the BookingAPI for Activities

Active Content – A solution to cache all static content associated or linked to an activity. This solution will prevent you from needing to include the content in the call and use the one previously downloaded. Presented in a structural way (XML format) allows to avoid calling the ContentAPI for Activities but still have the content available to be used.

If you rather prefer caching we recommend to you the following caching considerations or refresh periodicity (API and API call detailed, not all calls are present only the ones that are relevant for the caching): 

API

API Call

Refresh

Comments

Contents

Countries

Weekly

 

Contents

Languages

Weekly

 

Contents

Currencies

Weekly

 

Contents

Hotel

24 hours

These can be more than the ones being offered in the ContentAPI for Hotel. A hotel may not be bookable in the BookingAPI for Hotel but available as a pickup for an excursion in the BookingAPI for Activities.

Contents

Product Segments

6 hours

Categories that apply to a specific product (i.e. Family)

Contents

ContentsSimple

 

ContentsMulti

24 hours

If you would like to have all contents then use the Active Content solution to download all contents.

We recommend using the Service code as the key for caching.

Booking

Search

1 hour

Use the request as a key.

Allotment product could be available in the search but when confirming the allotment could be expired. If you would like to keep an allotment and pre-reserve it then you should use the pre-confirmation operation

Booking

Detail

DetailFull

Strongly advised not to be cached

Keep in mind that the rate keys required to confirm a product expire after 30 minutes.

Caching this operation may well be a mistake as you will incur in a higher probability of price differences between the detail and the confirmation.

Booking

RetrievePickups

1 hour

If a new product with pickups is appearing as available and pickups are not refreshed, a booking won’t be able to be performed.

Booking

Confirm

 

No need to be cached because you already storing it in your backoffice database as a confirmed booking

Booking

Modifications (all)

Strongly advised not to be cached

Just refresh the cached data in detail if a modification is performed.

Docs Navigation