This article covers two important practices that every site should follow to make the most efficient use of EAN's API and their own data: using compressed responses and slim response options.
First, check if your integration is accepting compressed API responses. If you haven't added this option to your site yet, it's easy: simply ensure all of your request headers include
Accept-Encoding: gzip, deflate. Data transfer times from EAN will be significantly reduced, as will bandwidth consumption.
Next, set up your integration to use slim response options to return smaller, tailored list and room responses. When used in conjunction with local copies of our static database files, you can rely on your own servers for static data rather than waiting to extract the data from our API responses.
You can find the biggest speed benefits by using this combination with the hotel list request. By setting the request's
options parameter to
ROOM_RATE_DETAILS, the hotel list response will return only dynamic rate information and a minimum of static identifying information. If you use the list request for simple availability checks or other situations where even dynamic rate data isn't necessary, you can send
HOTEL_SUMMARY for the slimmest and fastest possible response.
The room availability request features an
options parameter as well. You can choose to return only room types, amenities, images, etc. and supplement the rest with your own static databases.
For any instance where you use static database files, remember to keep your static databases up to date! Regardless of which of our database files you use or how you use them, you should refresh at least once per week to avoid errors and conflicting information.