- 4 New Ways We’re Changing the Way You Do Car Shopping
- A New Way to Book Lodging Made Easier
- Content Services for Lodging Migration Guide
- Content Services for Lodging Deep Dive Part 3: Checking Prices
- Content Services for Lodging Deep Dive Part 2: Getting Details
- Content Services for Lodging Deep Dive Part 1: Getting Availability
- Looking at Lodging APIs Part 2: What You Can Do with Them and Looking Forward
- Looking at Lodging APIs Part 1: Why We Built Them and How You Might See Them
- 6 Powerful Ways Content Services for Lodging Will Change How You Access Hotels Today
- October 2019
- September 2019
- July 2019
- June 2019
- May 2019
- March 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- March 2018
- January 2018
- November 2017
- October 2017
- August 2017
- July 2017
- June 2017
- May 2017
- March 2017
- January 2017
- December 2016
- November 2016
- September 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- December 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
Share this page
by Abby Messier
What’s the new EnhancedHotelBook API?
Are you currently implementing Content Services for Lodging into your booking tool? You may have already started your integration of our orchestrated or granular shopping APIs and now it’s time to look at booking.
Introducing the EnhancedHotelBook API, a new lodging SOAP/XML API allowing you to book both hotel GDS and new lodging aggregator content in a stateful environment, modify GDS bookings, and have full integration with your mid- and back-office products.
How It Works
The API performs several steps when booking a hotel room.
- It will decode and retrieve shopped rate details based on the data provided by the “Hotel Booking Key”.
- Depending on the data of the booking key and user input, the API will follow one of the following three strategies to book the desired hotel rate:
- Aggregator hotel via CSL
- GDS hotel via CSL
- GDS hotel as a legacy segment
- If the booking is successful, the API will validate the newly added segment statuses as returned by the hotel vendor (HK/SS/NN/PN/UC/NO):
- HK/SS/NN/PN are considered successful
- UC/NO are considered unsuccessful and the API will return an error
- Finally, it will return the current state of the session in the response payload (an internal call to TravelItineraryReadRQ).
Interested in learning more? Get access to the new EnhancedHotelBook API schemas, documentation and support materials here.
Other Booking Offerings to Explore
Like any offering out there, we know that one size doesn’t always fit all. We also know that no two workflows function the same. We want to make sure we’re here to help meet your needs, so that`s why we offer a few different options for you to connect to.
Here’s a quick guide to help you select the best Content Services for Lodging booking API fit for your workflow needs.